JDK-8235361 : JAR Class-Path no longer accepts relative URLs encoding absolute Windows paths (e.g "/C:/...")
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang:class_loading
  • Affected Version: 13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-12-04
  • Updated: 2019-12-17
  • Resolved: 2019-12-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 14
14 b27Fixed
Related Reports
Relates :  
JDK-8211941 - Enable checking/ignoring of non-conforming Class-Path entries
Relates :  
JDK-8218268 - Javac treats Manifest Class-Path entries as Paths instead of URLs
Description
Following JDK-8211941, et al, relative URLs that encode an absolute Windows file path (e.g., "/C:/path/to/file.jar") are ignored when used as entries in a JAR's Class-Path attribute.

This was discussed on core-libs-dev:
https://mail.openjdk.java.net/pipermail/core-libs-dev/2019-November/063491.html

A workaround is to use an absolute URL (e.g. "file:/C:/...").
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/336885e766af User: bchristi Date: 2019-12-10 20:09:25 +0000
10-12-2019