RE: Scanning multi version jars?

2017-09-18 Thread Stephen Felts
.        From: Greg Wilkins [mailto:gr...@webtide.com] Sent: Monday, September 18, 2017 9:33 PM To: Stephen Felts Cc: Paul Sandoz ; jigsaw-dev ; core-libs-dev@openjdk.java.net Subject: Re: Scanning multi

RE: Scanning multi version jars?

2017-09-18 Thread Stephen Felts
A versioned file name, JarEntry.getName(), starts with "META-INF/versions/". The version is the following string up to the next "/". The version can be parsed with Runtime.Version.parse(). If not a versioned class file name, then use Jarfile.baseVersion(). That should be sufficient to get the versi

RE: Scanning multi version jars?

2017-09-15 Thread Stephen Felts
FWIW I tracked down the MR jar file that I was having trouble with. It's the stand-alone JAXWS jar file com.sun.xml.ws.jaxws-rt.jar. Focusing on the problem class, the jar contains com/sun/xml/ws/util/xml/XmlCatalogUtil$1.class com/sun/xml/ws/util/xml/XmlCatalogUtil.class META-INF/versions/9/com/

RE: Java 9 build 148 causes trouble in Apache Lucene/Solr/Elasticsearch

2016-12-09 Thread Stephen Felts
ginal Message- From: Kevin Rushforth Sent: Friday, December 09, 2016 6:33 PM To: Stephen Felts Cc: Uwe Schindler; jigsaw-...@openjdk.java.net; Core-Libs-Dev Subject: Re: Java 9 build 148 causes trouble in Apache Lucene/Solr/Elasticsearch I second the recommendation of

RE: Java 9 build 148 causes trouble in Apache Lucene/Solr/Elasticsearch

2016-12-09 Thread Stephen Felts
world use cases and estimates of developer and end-user impact, are welcome". So you should make clear exactly API's that you want exposed. -Original Message- From: Uwe Schindler [mailto:uschind...@apache.org] Sent: Friday, December 09, 2016 6:22 PM To: Stephen Felts; jigsaw-

RE: Java 9 build 148 causes trouble in Apache Lucene/Solr/Elasticsearch

2016-12-09 Thread Stephen Felts
I would highly recommend running with _JAVA_OPTIONS=-Dsun.reflect.debugModuleAccessChecks=true It will tell you what add-options are required. One minor downside is that it will produce the warning in cases where the software is already correctly handling the exception from setAccessible, so the

RE: Java 9 build 148 causes trouble in Apache Lucene/Solr/Elasticsearch

2016-12-09 Thread Stephen Felts
Gradle/groovy are known to have problems with the restricted module access of b148.   You can get around this specific problem by using the environment variable _JAVA_OPTIONS=--add-opens=java.base/java.lang=ALL-UNNAMED   The packages that you need to open depend on what Java methods your gra