Re: Ready for JDK 9 ?

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

Re: Ready for JDK 9 ?

On Wed, Aug 9, 2017 at 1:00 PM, Ralph Goers wrote: > I have my doubts about the module system but I am not sure why you would > think multi-release jars will cause problems. > IIRC, multi-release jars causes problem in the Android tool chain. I imagine there are

Re: Ready for JDK 9 ?

I have my doubts about the module system but I am not sure why you would think multi-release jars will cause problems. Ralph > On Aug 9, 2017, at 8:28 AM, Gary Gregory wrote: > > On Wed, Aug 9, 2017 at 1:09 AM, Jörg Schaible < > joerg.schai...@bpm-inspire.com

Re: Ready for JDK 9 ?

Hi Jorg, Yes, I think rather just checking latest released source we should check the HEAD of components to ensure we will not break next planned release with java 9, at least we can fix if there is some issue from java9 RC it self, that will ensure future stability. Looking at commons-text

Re: Ready for JDK 9 ?

On Wed, Aug 9, 2017 at 1:09 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Hi Simon, > > Simon Spero wrote: > > > Compress HEAD is tested against the equivalent of RC. The main issues > were > > with tests; some types of mocking (especially of concrete classes) don't > > work. This

Re: Ready for JDK 9 ?

Hi Simon, Simon Spero wrote: > Compress HEAD is tested against the equivalent of RC. The main issues were > with tests; some types of mocking (especially of concrete classes) don't > work. This might have been fixed by now. > I believe that the latest jacoco is 9 compatible. > > [The biggest

Re: Ready for JDK 9 ?

Hi Amey, Amey Jadiye wrote: > Hmm, isn't that easy with just Travis ? We just have to add java9 > option(not sure it have RC) and trigger build it will automatically check > build and tests. IIRC for few components we are having java9 Travis env > already set. That would only ensure that the

Re: Ready for JDK 9 ?

://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

Re: Ready for JDK 9 ?

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

Re: Ready for JDK 9 ?

ent! 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

Re: Ready for JDK 9 ?

nificantly 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 sim

Re: Ready for JDK 9 ?

as module aware. But the compile checks should be easy to do.) Gruss Bernd Gruss Bernd -- http://bernd.eckenfels.net 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

Re: Ready for 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. D

Re: Ready for JDK 9 ?

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? Regards, Gilles or if there are any remaining show stopper issues which you've encountered when testing with the JDK 9 release candidate. JDK

Ready for JDK 9 ?

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