I didn't get the chance to reply when this thread happened, but really a project should only be viewed as JDK 9 ready when it has had a release with the Automatic-Module-Name entry in the manifest file. AFAIK, only common-lang has this (Although commons-csv, email and jcs were released recently I don't believe they have the entry).
Stephen On 8 August 2017 at 21:48, Pascal Schumacher <pascalschumac...@gmx.net> wrote: > Hello everybody, > > commons-lang and commons-text are build and tested with JDK 9 on traivs-ci, > e.g.: > > https://travis-ci.org/apache/commons-text/jobs/259838032 > https://travis-ci.org/apache/commons-lang/jobs/258653445 > > so I guess these components are ready for JDK 9. > > Cheers, > Pascal > > Am 08.08.2017 um 12:09 schrieb Rory O'Donnell: >> >> >> 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', >> or if there are any remaining show stopper issues which you've encountered >> when testing with the JDK 9 release candidate. >> >> JDK 9 b181 is available at http://jdk.java.net/9/ >> >> If you have a public web page, mailing list post, or even a tweet >> announcing you project's readiness for JDK 9, I'd love to add the URL to the >> upcoming JDK 9 readiness page on the Quality Outreach wiki. >> >> >> Looking forward to hearing from you, >> Rory >> >> [1] http://openjdk.java.net/projects/jdk9/ >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
