Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
RFC: Do not add CLASSPATH to the module path #5728
Treating the CLASSPATH as modules will create automatic modules for all entries that are not actually modules. This can lead to several problems, e.g. the automatic module name is determined by the name of the jar or directory, which fails when one component is not a valid java identifier. Another issue is that several automatic modules might export the same package, which is not allowed and leads to an error.
While the first problems is relatively easy to fix, the second one requires large changes and might not even possible if you are using third-party libraries (e.g. we are using UNO, which has problems with this).
To fix these issues, we can use the module path just for jruby libraries and pass the CLASSPATH using
Note that I haven't done extensive testing, because I first wanted to hear what you think about this approach.
Regarding your additional questions: