-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
P4
-
None
-
Affects Version/s: 21
-
Component/s: core-libs
-
x86_64
-
linux_debian_3.0
A DESCRIPTION OF THE PROBLEM :
This appears to be a JDK bug.
When a classpath element is specified directly via the -cp (or --class-path) option, symlinks are resolved.
When the same element is added via a JAR’s Class-Path manifest entry, symlinks are not resolved.
Internally, the jdk.internal.loader.URLClassPath helper is designed to ignore duplicate URLs, but it only does so when the URLs are byte-for-byte identical. If the same physical JAR file is referenced through multiple distinct URLs, it will be treated as separate entries and loaded multiple times.
This appears to be a JDK bug.
When a classpath element is specified directly via the -cp (or --class-path) option, symlinks are resolved.
When the same element is added via a JAR’s Class-Path manifest entry, symlinks are not resolved.
Internally, the jdk.internal.loader.URLClassPath helper is designed to ignore duplicate URLs, but it only does so when the URLs are byte-for-byte identical. If the same physical JAR file is referenced through multiple distinct URLs, it will be treated as separate entries and loaded multiple times.