Java 9 Support

[Paul Merlin <pa...@apache.org>]

Gang,

Good news, Zest Core just works on Java 9!

Bad news, we can't just use it right now.
Some things in the build are failing with Java 9.

I created ZEST-175 to track the effort.

Code wise, only one test was failing with Java 9 because it uses 
internal JDK apis.
It's the test for virtual hosting setup in HTTP Library that failed, it 
hooks into the JVM DNS resolution to setup the test environment. I moved 
it in a separate source-set that is only used when the build is run with 
JDK<9. That's good enough.

I did upgrade ./gradlew to use Gradle 3.0 along the way as it was needed 
to support Java 9.
You'll notice that the Gradle Daemon is now enabled by default, see 
https://docs.gradle.org/3.0/release-notes.
I explicitly disabled the daemon on CI.

I also added a CI job to ensure we don't introduce anything that would 
prevent Zest to work on JDK 9:
https://builds.apache.org/view/S-Z/view/Zest/job/Zest(JavaEdition)-develop-java9-check/

Three things remain:

1/ OSGi/Bnd does not support Java 9 yet.
2/ The Scala compiler does not support Java 9 yet.
3/ Jacoco does not support Java 9 yet, their 0.7.8-SNAPSHOT version do.

I'll upgrade these as soon as compatible versions are published.

Cheers

/Paul

Re: Java 9 Support

[Sandro Martini <sa...@gmail.com>]

Hi Paul,
as always you did a great job !!

Bye,
Sandro


2016-09-05 3:46 GMT+02:00 Paul Merlin <pa...@apache.org>:
> Gang,
>
> Good news, Zest Core just works on Java 9!
>
> Bad news, we can't just use it right now.
> Some things in the build are failing with Java 9.
>
> I created ZEST-175 to track the effort.
>
> Code wise, only one test was failing with Java 9 because it uses internal
> JDK apis.
> It's the test for virtual hosting setup in HTTP Library that failed, it
> hooks into the JVM DNS resolution to setup the test environment. I moved it
> in a separate source-set that is only used when the build is run with JDK<9.
> That's good enough.
>
> I did upgrade ./gradlew to use Gradle 3.0 along the way as it was needed to
> support Java 9.
> You'll notice that the Gradle Daemon is now enabled by default, see
> https://docs.gradle.org/3.0/release-notes.
> I explicitly disabled the daemon on CI.
>
> I also added a CI job to ensure we don't introduce anything that would
> prevent Zest to work on JDK 9:
> https://builds.apache.org/view/S-Z/view/Zest/job/Zest(JavaEdition)-develop-java9-check/
>
> Three things remain:
>
> 1/ OSGi/Bnd does not support Java 9 yet.
> 2/ The Scala compiler does not support Java 9 yet.
> 3/ Jacoco does not support Java 9 yet, their 0.7.8-SNAPSHOT version do.
>
> I'll upgrade these as soon as compatible versions are published.
>
> Cheers
>
> /Paul
>

Re: Java 9 Support

[Paul Merlin <pa...@nosphere.org>]

Hey Niclas,

I tried both with and without Jigsaw enabled. The core is OK either way.

The Jigsaw enabled build of JDK 9 I had handy last week was a bit old. I 
tried with a more recent build this weekend and found that there will be 
more things to fix in a few core tests and around libraries and 
extensions.

I started updating all the 3rd party libraries we use. Some of these 
upgrades bring Java 9 support, some Jigsaw support, some nothing except 
being closer to new versions to come that will enable Java 9/Jigsaw 
support.

For 3.0 we should only aim at running OK on Java 9 & Jigsaw, we'll see 
how to leverage Jigsaw later ;-)

To be continued

Cheers


Le 2016-09-06 03:18, Niclas Hedhman a �crit�:
> Cool. I have not studied Java 9 one bit, but I heard that JIgsaw 
> introduces
> a modular packaging system, which has a different establishment of 
> class
> searches, than the linear classpath approach that we are used to.
> 
> Did your test run this new modular classloading and/or the "legacy" 
> way??
> 
> 
> My guess is that there is opportunity to leverage the modular system in
> Java 9, but it is really too early to have good ideas around it, 
> especially
> since it is unclear how it fits in with OSGi.
> 
> 
> Cheers
> Niclas

Re: Java 9 Support

[Niclas Hedhman <ni...@hedhman.org>]

Cool. I have not studied Java 9 one bit, but I heard that JIgsaw introduces
a modular packaging system, which has a different establishment of class
searches, than the linear classpath approach that we are used to.

Did your test run this new modular classloading and/or the "legacy" way??


My guess is that there is opportunity to leverage the modular system in
Java 9, but it is really too early to have good ideas around it, especially
since it is unclear how it fits in with OSGi.


Cheers
Niclas

On Mon, Sep 5, 2016 at 9:46 AM, Paul Merlin <pa...@apache.org> wrote:

> Gang,
>
> Good news, Zest Core just works on Java 9!
>
> Bad news, we can't just use it right now.
> Some things in the build are failing with Java 9.
>
> I created ZEST-175 to track the effort.
>
> Code wise, only one test was failing with Java 9 because it uses internal
> JDK apis.
> It's the test for virtual hosting setup in HTTP Library that failed, it
> hooks into the JVM DNS resolution to setup the test environment. I moved it
> in a separate source-set that is only used when the build is run with
> JDK<9. That's good enough.
>
> I did upgrade ./gradlew to use Gradle 3.0 along the way as it was needed
> to support Java 9.
> You'll notice that the Gradle Daemon is now enabled by default, see
> https://docs.gradle.org/3.0/release-notes.
> I explicitly disabled the daemon on CI.
>
> I also added a CI job to ensure we don't introduce anything that would
> prevent Zest to work on JDK 9:
> https://builds.apache.org/view/S-Z/view/Zest/job/Zest(JavaEd
> ition)-develop-java9-check/
>
> Three things remain:
>
> 1/ OSGi/Bnd does not support Java 9 yet.
> 2/ The Scala compiler does not support Java 9 yet.
> 3/ Jacoco does not support Java 9 yet, their 0.7.8-SNAPSHOT version do.
>
> I'll upgrade these as soon as compatible versions are published.
>
> Cheers
>
> /Paul
>
>


-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java