Hi Steve, Thanks for the quick fix! I am not able to test this on the short term, but I trust you that Lucene builds now. I am a bit nervous, because it does not explain the Ivy issues, but I will try to create some test cases with relative jar:-URL resolving tomorrow. This may help with resolving the problems in build 110.
I just want to make sure, that the following also works: - Get URL from classloader to a resource file - resolve a relative file against this URL and load it by URL (this is common pattern for parsing XML resources from JAR files that refer relatively to other resources in same JAR file by href) Keep me informed when build 109 is downloadable. Uwe ----- Uwe Schindler uschind...@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany http://lucene.apache.org/ > -----Original Message----- > From: core-libs-dev [mailto:core-libs-dev-boun...@openjdk.java.net] On > Behalf Of Steve Drach > Sent: Monday, March 07, 2016 8:07 PM > To: core-libs-dev <core-libs-dev@openjdk.java.net>; paul Sandoz > <paul.san...@oracle.com>; Alan Bateman <alan.bate...@oracle.com>; > Xueming Shen <xueming.s...@oracle.com> > Subject: RFR: 8151339 Adding fragment to JAR URLs breaks ant > > Hi, > > Please review the following changeset. We’d like to get this into build 109, > which means by noon today. This is essentially a temporary fix, but it’s been > tested and Lucene has been built against it. We will follow up with a more > comprehensive fix by build 110. > > webrev: http://cr.openjdk.java.net/~sdrach/8151339/webrev/ > <http://cr.openjdk.java.net/~sdrach/8151339/webrev/> > issue: https://bugs.openjdk.java.net/browse/JDK-8151339 > <https://bugs.openjdk.java.net/browse/JDK-8151339> > > Thanks > Steve >
