Scaladoc doesn't need any bootstrapping, otherwise will create errors such as: [scaladoc] ../scala-trunk/src/reflect/scala/reflect/macros/Reifiers.scala:89: error: object api is not a member of package reflect [scaladoc] case class ReificationException(val pos: reflect.api.PositionApi, val msg: String) extends Throwable(msg) [scaladoc] ^ because the bootstrapping will look at the sourcepath and create package "reflect" in "<root>" and then when typing relative names, instead of picking <root>.scala.relect, typedIdentifier will pick up the <root>.reflect package created by the bootstrapping. Thus, no bootstrapping for scaladoc! TODO: we should refactor this as a separate -bootstrap option to have a clean implementation, no?
Against my better judgment, giving in to martin here and allowing CLASSPATH to be used automatically.
Against my better judgment, giving in to martin here and allowing CLASSPATH to be used automatically. So for the user-specified part of the classpath:
Calculated values based on any given command line options, falling back on those in Defaults.