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
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
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
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
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
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
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
The same goes for commons-compress (as already mentioned by Simon Spero):
https://travis-ci.org/apache/commons-compress/jobs/258642081
Am 08.08.2017 um 22:48 schrieb Pascal Schumacher:
Hello everybody,
commons-lang and commons-text are build and tested with JDK 9 on
traivs-ci, e.g.:
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
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.
Regards,
Amey
On Tue, Aug 8, 2017, 8:38 PM Jörg Schaible
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 problem was caused by a bug in the zip code
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
Hi,
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
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
14 matches
Mail list logo