From 03be20907b23be59f33ab9f2e07dd0174e9d37cd Mon Sep 17 00:00:00 2001 From: eugene yokota Date: Thu, 18 Apr 2019 11:03:29 -0400 Subject: [PATCH] Updated Scala modularization and classpaths (markdown) --- Scala-modularization-and-classpaths.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Scala-modularization-and-classpaths.md b/Scala-modularization-and-classpaths.md index 1dff140..2375074 100644 --- a/Scala-modularization-and-classpaths.md +++ b/Scala-modularization-and-classpaths.md @@ -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/`. -## 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. This is not the right thing to do because it makes available classes not on the user's classpath.