The javac documentation section entitled "Searching for Module, Package and Type Declarations" fails to mention how javac dynamically extends the class search path by interpreting class-path manifest attributes in JARs that it examines. This behavior can be surprising [1], so it needs to be documented.
[1] https://dzone.com/articles/jar-manifest-class-path-is-not-for-java-applicatio
[1] https://dzone.com/articles/jar-manifest-class-path-is-not-for-java-applicatio
- relates to
-
JDK-4212732 javac seems to ignore classpath manifest entries in jar files
- Resolved
- links to
-
Review openjdk/jdk/13332
-
Review(master) openjdk/jdk/22243