From 5995679f04eebfdf03d64d315997d073f6f028e7 Mon Sep 17 00:00:00 2001 From: eugene yokota Date: Thu, 18 Apr 2019 11:33:52 -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 24ea46a..908fbfd 100644 --- a/Scala-modularization-and-classpaths.md +++ b/Scala-modularization-and-classpaths.md @@ -6,7 +6,9 @@ Scala modularization makes it necessary to deal with some existing issues that m 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). -The Scala compiler has `-javabootclasspath ` flag to override Java boot classpath. I assume the intent is to allow overriding classes in Java standard library. +`javac` supports programmers wanting to resolve boot class (or extension class) references using an alternative Java platform implementation by providing `-bootclasspath` options. + +The Scala compiler also provides `-javabootclasspath ` flag to override Java boot classpath. For the Java boot classpath, the `scala` script justs puts everything in `lib/` on it. This is not the right thing to do because it makes classes not on the user's classpath available.