I am willing to do that for a few components. Maybe we can collect the Java9 
state for commons on a Wiki Page, like:

Component | Compiles with 9 since | Module aware? | Latest bin Release runs in 
9. | Comments....

(Not sure how easy the modules check will be and what we define as module 
aware. But the compile checks should be easy to do.)


From: Jörg Schaible <joerg.schai...@bpm-inspire.com>
Sent: Tuesday, August 8, 2017 5:07:54 PM
To: dev@commons.apache.org
Subject: Re: Ready for JDK 9 ?


Gilles wrote:

> Hi.
> On Tue, 8 Aug 2017 11:09:01 +0100, Rory O'Donnell wrote:
>> Hi Benedikt,
>> Thank you very much for all your testing of JDK 9 during its
>> development! Such contributions have significantly helped shape and
>> improve JDK 9.
>> Now that we have reached the JDK 9 Final Release Candidate phase [1]
>> , I would like to ask if your project can be considered to be 'ready
>> for JDK 9',
> Is there some simple thing to do in order to be able to answer
> that question?

IMHO no. Definitelly not in general for all components. Practically we would
have to checkout the latest releases from source (or use the source
tarballs) and run at least the unit tests with this Java 9 RC.


To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to