Hi Rory,
I already opened an issue for forbidden-apis checker: https://code.google.com/p/forbidden-apis/issues/detail?id=39 In Lucene we have no traversal of bootclasspath (we only inspect our application classpath in tests to enumerate test classes, which will not change by the JEP). In general, I expect projects like Apache Ant and Apache Maven to have problems with the new classpath layout, because they all rely on stuff like rt.jar available. The main problem (from the perspective of a tools developer) is the fact that Classloader has no possibility to list all resources/classes from a specific Java package. This is still not addressed in the JEP (it is party by the new FilesystemProvider for jrt:/ URLs), but there is no generic way for tools to list classes or resources. You always need some knowledge about the structure of your classpath, which is bad! Something like ClassLoader#getClassesInPackage() or ClassLoader#getResourcesInPackage and ClassLoader.listPackages() is needed (my personal opinion). Alternatively a very general FileSystemProvider for the whole Classpath not just the runtime packages would be cool. Interestingly, in the new issue of the German Java Magazin, Arno Haase wrote an article about traversing the classpath… One big problem is also that some parts of the new infrastructure also need the tools be compiled against newer JDKs (because Filesystem API is only available with Java 7), but Tools like Apache Ant or Maven are still comiled against JDK5 for compatibility reasons. For those projects its hard to make use of the filesystem providers, so they need to update or use some “shim” classes if they detect a new JDK version. Uwe ----- Uwe Schindler uschind...@apache.org Apache Lucene PMC Member / Committer Bremen, Germany http://lucene.apache.org/ From: quality-discuss [mailto:quality-discuss-boun...@openjdk.java.net] On Behalf Of Rory O'Donnell Sent: Friday, October 31, 2014 10:10 AM To: Martijn Verburg Cc: quality-discuss@openjdk.java.net; adoption-disc...@openjdk.java.net Subject: Re: Fwd: FYI: Next Jigsaw JEP posted Hi Martijn, We are still working the Quality group lead issue, in the mean time I will work with Dalibor on this an come back to you. I will ping all the FOSS projects listed on the Quality Outreach wiki <https://wiki.openjdk.java.net/display/Adoption/Quality+Outreach> asking them to test their tools, libraries, and applications against these builds to help tease out any compatibility issues. Rgds,Rory On 31/10/2014 08:57, Martijn Verburg wrote: Hi Rory, Does the quality group have a wiki? I'm thinking that we list the areas to test and how to test them there and then have both Jigsaw and Adoption groups link to that material, we can probably use the Adoption GitHub group to build any code tutorials (like with lambdas and date and time). Cheers, Martijn On 31 October 2014 08:30, Rory O'Donnell <rory.odonn...@oracle.com> wrote: Thanks Martijn, Will let you all know when the EA builds become available, your help with testing these builds will be much appreciated. Rgds,Rory On 30/10/2014 17:33, Martijn Verburg wrote: Cheers, Martijn ---------- Forwarded message ---------- From: <mark.reinh...@oracle.com> Date: 30 October 2014 17:30 Subject: FYI: Next Jigsaw JEP posted To: jdk9-...@openjdk.java.net http://openjdk.java.net/jeps/220 -- Modular Run-Time Images This JEP will soon be proposed for JDK 9. Please direct questions and comments to the jigsaw-dev list. - Mark -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
