JDK-8151339 : Adding fragment to JAR URLs breaks ant
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 9
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-03-05
  • Updated: 2016-09-23
  • Resolved: 2016-03-07
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 9
9 b109Fixed
Related Reports
Relates :  
JDK-8151542 - URL resources for multi-release jar files have a #runtime fragment appended to them
Relates :  
JDK-8132734 - JDK 9 runtime changes to java.util.jar to support multi-release jar files
Description

http://mail.openjdk.java.net/pipermail/core-libs-dev/2016-March/039303.html
Comments
I talked with Paul today on this and we are agreement that the MR JAR support needs to backed out of JDK 9 until all the issues related to URLs are understood and can be handled without breaking the world.
07-03-2016
Another sighting from Uwe: "after patching Apache Ant, I found the next problem with Multi-Release JAR files: This time the other way round! The "#release" fragment broke the next part of the Lucene build system: Apache Ivy (which is responsible to download artifacts from Maven Central and is used by Ant and Gradle)! Apache Ivy seems to build its JAR file URLs on its own, not adding the #release fragment. JARURLConnection then throws FileNotFoundException..."
07-03-2016