CI @ JDK 16 (dropping JDK 15)

97 views
Skip to first unread message

Falko

unread,
May 2, 2021, 6:41:55 PM5/2/21
to Quarkus Development mailing list

Hi everyone,

Guillaume Smet asked me to summarize the current state so here we go:

The details are in the respective issue [1]. I'm not completely done with analyzing/fixing things, but I'd say I'm at ~80%.

For now, I see the following main points to discuss/address before JDK 16 replaces the JDK 15 job(s):
- Wait until upgrade to Kotlin 1.5 is done or live with global "--add-opens java.base/java.util=ALL-UNNAMED" for a while?
- Wait until upgrade to Gradle 7 is done or live with exclusion of all Gradle bits for a while?
  Alternatively, toolchain support could be leveraged for Gradle 6.

My opinion: I wouldn't wait for those ugrades, JDK15 is already dead.

The other fixes (see [2]) are more or less ok IMO but of course we should eliminate those workarounds as well over time, e.g. by upgrading to XStream 1.5 etc.

WDYT?


Cheers,
Falko

moldowan

unread,
May 3, 2021, 4:38:31 PM5/3/21
to Max Andersen, quark...@googlegroups.com
Seems you forgot to send this to the list? Anyway:

Where is that global all opens to be set? On all of our quarkus build test runs not just the kotlin related ones ?
Right now it is only set for the entire EA job but once I get this green, I'll have to see where to add it: basically for all jobs that run the kotlin-maven-plugin.

About gradle we would need both gradle 6 and 7 testing I would imagine.
Well, ideally yes, I suppose. Would be interesting to hear what Guillaume Le Floch thinks about this.

Cheers,
Falko

Am 03.05.2021 um 07:46 schrieb Max Andersen:
Thanks for looking into it. 

Where is that global all opens to be set? On all of our quarkus build test runs not just the kotlin related ones ?

About gradle we would need both gradle 6 and 7 testing I would imagine. Gradle 6 isn’t exactly going away any time soon so if toolchains can be set up that makes sense to me. 
--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/901b6623-bb03-490b-a67e-72bb58df1e1cn%40googlegroups.com.


Falko

unread,
May 3, 2021, 6:10:00 PM5/3/21
to Quarkus Development mailing list
A few test failures slipped through and so the party is not over yet.

I fixed a few minor ones today, will continue tomorrow - slowly but surely.

I will continue to ping people in the issue, asking for support. Any help is very much appreciated!

Cheers,
Falko

Falko

unread,
May 8, 2021, 10:55:45 AM5/8/21
to Quarkus Development mailing list
CI made the switch from 15 to 16 and the nightly EA job now runs on 17-ea (hitting many issues, as expected).

There are a couple of clean ups to improve Java 16 compatibility (possibly user visible!) :
- and to some extend: https://github.com/quarkusio/quarkus/issues/16862 (so that user can more easily pass --add-open etc. if needed)

Cheers,
Falko
Reply all
Reply to author
Forward
0 new messages