Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java.class.path, Jar files and directory expansion. #992

Open
ed03875 opened this issue Mar 27, 2019 · 0 comments
Open

Java.class.path, Jar files and directory expansion. #992

ed03875 opened this issue Mar 27, 2019 · 0 comments
Labels
bug Issues that are problems in the code as reported by the community

Comments

@ed03875
Copy link

ed03875 commented Mar 27, 2019

This problem presents on W64 and Linux in two different distributions of OpenJDK Java 11 that we know of : openjdk version "11.0.2" 2019-01-15 and openjdk version "11.0.1" 2018-10-16.

Windows 10
Linux 3.10.0-862.3.2.el7.x86_64 #1 SMP Mon May 21 23:36:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I must be missing something obvious because I would have thought that others would have found this behaviour long before now. When starting the JVM and setting the system property java.class.path to point to directories and not specific jar files as shown here "-Djava.class.path=C:\directory\rmeval;.c:\fixes\bin\w64\bin\jvm\ext;" we find that classes that are known to be in the jars in the directories are not found. If we point to the jar specifically , the classes are found. Wildcards also have the same problem. for example "-Djava.class.path=C:\directory\rmeval*.jar;.c:\fixes\jvm\ext*;"

Has this functionality been removed from Java 11 ? We have a rather large product where it is not reasonable to specify each jar file used on the class path.

@karianna karianna added the bug Issues that are problems in the code as reported by the community label Mar 27, 2019
@karianna karianna modified the milestones: March 2019, April 2019 Mar 27, 2019
@karianna karianna modified the milestones: April 2019, May 2019 May 1, 2019
@karianna karianna modified the milestones: May 2019, June 2019 Jun 3, 2019
@karianna karianna modified the milestones: June 2019, July 2019 Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are problems in the code as reported by the community
Projects
Status: Todo
Development

No branches or pull requests

2 participants