Fwd: FYI: Next Jigsaw JEP posted

Uwe Schindler uschindler at apache.org
Fri Oct 31 09:53:15 UTC 2014

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 Schindler

uschindler at apache.org 

Apache Lucene PMC Member / Committer

Bremen, Germany



From: quality-discuss [mailto:quality-discuss-bounces at openjdk.java.net] On Behalf Of Rory O'Donnell
Sent: Friday, October 31, 2014 10:10 AM
To: Martijn Verburg
Cc: quality-discuss at openjdk.java.net; adoption-discuss at 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.

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).



On 31 October 2014 08:30, Rory O'Donnell <rory.odonnell at 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.

On 30/10/2014 17:33, Martijn Verburg wrote:


---------- Forwarded message ----------
From: <mark.reinhold at oracle.com>
Date: 30 October 2014 17:30
Subject: FYI: Next Jigsaw JEP posted
To: jdk9-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20141031/6b93d134/attachment-0001.html>

More information about the quality-discuss mailing list