Updated Scala modularization and classpaths (markdown)

eugene yokota 2019-04-18 11:03:29 -04:00
parent f630315270
commit 03be20907b
1 changed files with 3 additions and 1 deletions

@ -2,7 +2,9 @@
Scala modularization makes it necessary to deal with some existing issues that mainly relate to the (Java) boot classpath and to using Scala jars from a `lib/`. Scala modularization makes it necessary to deal with some existing issues that mainly relate to the (Java) boot classpath and to using Scala jars from a `lib/`.
## Java boot classpath ## Java boot classpath (bootstrap classpath)
The term "boot classpath" comes from Java's Bootstrap Classes, which are the classes that implement the Java Platform. By default, bootstrap classes are in the `rt.jar` and several other jar files in the `jre/lib` directory according to [How Classes are Found](https://docs.oracle.com/javase/8/docs/technotes/tools/findingclasses.html).
For the Java boot classpath, the `scala` launcher justs puts everything in `lib/` on it. For the Java boot classpath, the `scala` launcher justs puts everything in `lib/` on it.
This is not the right thing to do because it makes available classes not on the user's classpath. This is not the right thing to do because it makes available classes not on the user's classpath.