[hibernate-dev] Re: [External] : Re: JDK 18 Rampdown Phase 2 & JDK 19 Early-Access Builds

[Yoann Rodiere]

For what it's worth, build 8 seems to be available [1], so it's apparently
just a matter of updating the links on https://jdk.java.net/19/ (and in our
CI).

As someone participating in the Quality Outreach program, I would like to
suggest that you keep a given build available for download at least until
participating projects are notified there's a new build that replaces the
previous one. I.e. keep JDK 9-ea+7 available until we get an email telling
us to test JDK 9-ea+9. This would make the process much smoother on our
side.

[1]
https://download.java.net/java/early_access/jdk19/8/GPL/openjdk-19-ea+8_linux-x64_bin.tar.gz

Yoann Rodière
Hibernate Team
yo...@hibernate.org


On Fri, 4 Feb 2022 at 12:42, Yoann Rodiere  wrote:

> Hey David,
>
> It seems the download links on https://jdk.java.net/19/ are out of date;
> the link for Linux / x64 in particular [1] is giving me a 404.
>
> This is making our continuous integration fail, so we might end up
> disabling JDK 19 tests unless we find a solution soon...
>
> Do you think you could look into this?
>
> [1]
>
> https://download.java.net/java/early_access/jdk19/7/GPL/openjdk-19-ea+7_linux-x64_bin.tar.gz
>
> Thanks,
>
> Yoann Rodière
> Hibernate Team
> yo...@hibernate.org
>
>
> On Fri, 4 Feb 2022 at 10:36, David Delabassee  >
> wrote:
>
> > Salut Yoann,
> >
> > As always, thanks for the feedback!
> >
> > There has been no ASM release since
> >
> https://gitlab.ow2.org/asm/asm/-/commit/33a3c0e1852323eb024860ad05269403069afa50
> ,
> > that could explain the problem you're facing with Gradle and EA19.
> >
> > Thanks,
> >
> > --David
> >
> >
> > On 02/02/2022 12:20, Yoann Rodiere wrote:
> >
> > Hello David,
> >
> > All is well for Hibernate projects on JDK 18.
> >
> > I'm having trouble running the Gradle builds on JDK19, though: even
> > running Gradle itself on JDK11, it seems Gradle is unable to use JDK19
> as a
> > toolchain. I'm still investigating and will report where appropriate
> (it's
> > probably a Gradle bug).
> >
> > Summary for the wiki:
> >
> > Hibernate ORM: Versions 5.6 and 6.0 tested against JDK 18 EA33. No
> > problems to report.
> >
> > Hibernate Validator: Version 7.0 tested against JDK 18 EA33 and JDK 19
> > EA7. No problems to report.
> >
> > Hibernate Search: Version 6.1 tested against JDK 18 EA33 and JDK 19 EA7.
> > No problems to report.
> >
> > Hibernate Reactive: Version 1.1 tested against JDK 18 EA33. No problems
> to
> > report.
> >
> >
> > Yoann Rodière
> > Hibernate Team
> > yo...@hibernate.org
> >
> >
> > On Mon, 31 Jan 2022 at 12:58, David Delabassee <
> > david.delabas...@oracle.com> wrote:
> >
> >> Greetings!
> >>
> >> First off, on behalf of Oracle’s Java Team, I’d like to wish you a happy
> >> and prosperous new year!
> >>
> >> In 2022, two Java releases will be made available:
> >> - JDK 18 (March 2022)
> >> - JDK 19 (September 2022)
> >>
> >> JDK 18[1] has entered Rampdown Phase Two (RDP2)[2]. Given that and to be
> >> better prepared for the future, it makes sense to begin testing your
> >> project(s) using early access (EA) builds of JDK 19[3]. Your feedback
> >> allows us to evaluate and address issues you find while testing EA
> builds.
> >>
> >> This time, we have two heads-up to share:
> >>
> >> ## Heads-Up: JDK 18 - JEP 421 Deprecate Finalization for Removal
> >>
> >> Finalization is an outdated and brittle resource cleaning mechanism
> >> present in the platform since, well, forever. Its use has been
> >> discouraged for quite some time in favor of better alternatives (i.e.,
> >> 'try with resources' and Cleaners). JEP 421 is another step towards the
> >> removal of finalizers as it offers tools to investigate if a codebase is
> >> still using finalization. To learn more, you should read JEP 421[4]. You
> >> should also listen to the latest episode of the Inside Java Podcast[5]
> >> dedicated to this topic. We encourage you to check if your project is
> >> still using finalizers. If so, you should start to think about removing
> >> them and rely instead on either 'try with resources' or Cleaners.
> >>
> >> ## Heads-Up: JVM does not flag constant class entries ending in '/'
> >>
> >> Prior to JDK 19, the JVM is loading classes (1) whose class file major
> >> version is <49, i.e., before JDK 1.5, and (2) the class's name ends with
> >> a '/'. This violates section 4.2.1 of the JVM specification [6] and is
> >> addressed in JDK 19. In JDK 19, the JVM is throwing, for such classes, a
> >> ClassFormatError exception as it already does with newer classes (JDK
> >> 1.5+). Given that this issue affects only pre-JDK 1.5 classes, we expect
> >> the compatibility risk to be very low.
> >>
> >> For more details, see JDK-8278448[7].
> >>
> >> [1] https://jdk.java.net/18/
> >> <
> https://urldefense.com/v3/__https://jdk.java.net/18/__;!!ACWV5N9M2RV99hQ!d9v7ZDgoXgRTA6rmUmI-zmmZ25r7qapNxj75iRC_6Y7dJqde5LsMZGXSYDxQRCRWFo2s$
> >
> >> [2]
> >>
> https://mail.openjdk.java.net/pipermail/jdk-dev/2022-January/006361.html
> >> [3] 

[hibernate-dev] Re: [External] : Re: JDK 18 Rampdown Phase 2 & JDK 19 Early-Access Builds

[David Delabassee]

Salut Yoann,

As always, thanks for the feedback!

There has been no ASM release since 
https://gitlab.ow2.org/asm/asm/-/commit/33a3c0e1852323eb024860ad05269403069afa50, 
that could explain the problem you're facing with Gradle and EA19.


Thanks,

--David


On 02/02/2022 12:20, Yoann Rodiere wrote:

Hello David,

All is well for Hibernate projects on JDK 18.

I'm having trouble running the Gradle builds on JDK19, though: even 
running Gradle itself on JDK11, it seems Gradle is unable to use JDK19 
as a toolchain. I'm still investigating and will report where 
appropriate (it's probably a Gradle bug).


Summary for the wiki:

Hibernate ORM: Versions 5.6 and 6.0 tested against JDK 18 EA33. No 
problems to report.


Hibernate Validator: Version 7.0 tested against JDK 18 EA33 and JDK 19 
EA7. No problems to report.


Hibernate Search: Version 6.1 tested against JDK 18 EA33 and JDK 19 
EA7. No problems to report.


Hibernate Reactive: Version 1.1 tested against JDK 18 EA33. No 
problems to report.




Yoann Rodière
Hibernate Team
yo...@hibernate.org


On Mon, 31 Jan 2022 at 12:58, David Delabassee 
 wrote:


Greetings!

First off, on behalf of Oracle’s Java Team, I’d like to wish you a
happy
and prosperous new year!

In 2022, two Java releases will be made available:
- JDK 18 (March 2022)
- JDK 19 (September 2022)

JDK 18[1] has entered Rampdown Phase Two (RDP2)[2]. Given that and
to be
better prepared for the future, it makes sense to begin testing your
project(s) using early access (EA) builds of JDK 19[3]. Your feedback
allows us to evaluate and address issues you find while testing EA
builds.

This time, we have two heads-up to share:

## Heads-Up: JDK 18 - JEP 421 Deprecate Finalization for Removal

Finalization is an outdated and brittle resource cleaning mechanism
present in the platform since, well, forever. Its use has been
discouraged for quite some time in favor of better alternatives
(i.e.,
'try with resources' and Cleaners). JEP 421 is another step
towards the
removal of finalizers as it offers tools to investigate if a
codebase is
still using finalization. To learn more, you should read JEP
421[4]. You
should also listen to the latest episode of the Inside Java
Podcast[5]
dedicated to this topic. We encourage you to check if your project is
still using finalizers. If so, you should start to think about
removing
them and rely instead on either 'try with resources' or Cleaners.

## Heads-Up: JVM does not flag constant class entries ending in '/'

Prior to JDK 19, the JVM is loading classes (1) whose class file
major
version is <49, i.e., before JDK 1.5, and (2) the class's name
ends with
a '/'. This violates section 4.2.1 of the JVM specification [6]
and is
addressed in JDK 19. In JDK 19, the JVM is throwing, for such
classes, a
ClassFormatError exception as it already does with newer classes (JDK
1.5+). Given that this issue affects only pre-JDK 1.5 classes, we
expect
the compatibility risk to be very low.

For more details, see JDK-8278448[7].

[1] https://jdk.java.net/18/


[2]
https://mail.openjdk.java.net/pipermail/jdk-dev/2022-January/006361.html
[3] https://jdk.java.net/19/


[4] https://openjdk.java.net/jeps/421
[5] https://inside.java/podcast/21


[6]
https://docs.oracle.com/javase/specs/jvms/se17/html/jvms-4.html#jvms-4.2.1
[7] https://bugs.openjdk.java.net/browse/JDK-8278448


## JDK 18

JDK 18 is now in RDP2 (Rampdown Phase Two) with its feature set
frozen a
few weeks back when it entered RDP1.

### JEPs integrated to JDK 18:

- JEP 400: UTF-8 by Default
- JEP 408: Simple Web Server
- JEP 413: Code Snippets in Java API Documentation
- JEP 416: Reimplement Core Reflection with Method Handles
- JEP 417: Vector API (Third Incubator)
- JEP 418: Internet-Address Resolution SPI
- JEP 419: Foreign Function & Memory API (Second Incubator)
- JEP 420: Pattern Matching for switch (Second Preview)
- JEP 421: Deprecate Finalization for Removal

JDK 18 Early-Access builds 33 are now available[8], and are provided
under the GNU General Public License v2, with the Classpath
Exception.
Also available are the Release Notes[9].

[8] https://jdk.java.net/18/

[hibernate-dev] Re: [External] : Re: JDK 18 Rampdown Phase 2 & JDK 19 Early-Access Builds

[Yoann Rodiere]

Hey David,

It seems the download links on https://jdk.java.net/19/ are out of date;
the link for Linux / x64 in particular [1] is giving me a 404.

This is making our continuous integration fail, so we might end up
disabling JDK 19 tests unless we find a solution soon...

Do you think you could look into this?

[1]
https://download.java.net/java/early_access/jdk19/7/GPL/openjdk-19-ea+7_linux-x64_bin.tar.gz

Thanks,

Yoann Rodière
Hibernate Team
yo...@hibernate.org


On Fri, 4 Feb 2022 at 10:36, David Delabassee 
wrote:

> Salut Yoann,
>
> As always, thanks for the feedback!
>
> There has been no ASM release since
> https://gitlab.ow2.org/asm/asm/-/commit/33a3c0e1852323eb024860ad05269403069afa50,
> that could explain the problem you're facing with Gradle and EA19.
>
> Thanks,
>
> --David
>
>
> On 02/02/2022 12:20, Yoann Rodiere wrote:
>
> Hello David,
>
> All is well for Hibernate projects on JDK 18.
>
> I'm having trouble running the Gradle builds on JDK19, though: even
> running Gradle itself on JDK11, it seems Gradle is unable to use JDK19 as a
> toolchain. I'm still investigating and will report where appropriate (it's
> probably a Gradle bug).
>
> Summary for the wiki:
>
> Hibernate ORM: Versions 5.6 and 6.0 tested against JDK 18 EA33. No
> problems to report.
>
> Hibernate Validator: Version 7.0 tested against JDK 18 EA33 and JDK 19
> EA7. No problems to report.
>
> Hibernate Search: Version 6.1 tested against JDK 18 EA33 and JDK 19 EA7.
> No problems to report.
>
> Hibernate Reactive: Version 1.1 tested against JDK 18 EA33. No problems to
> report.
>
>
> Yoann Rodière
> Hibernate Team
> yo...@hibernate.org
>
>
> On Mon, 31 Jan 2022 at 12:58, David Delabassee <
> david.delabas...@oracle.com> wrote:
>
>> Greetings!
>>
>> First off, on behalf of Oracle’s Java Team, I’d like to wish you a happy
>> and prosperous new year!
>>
>> In 2022, two Java releases will be made available:
>> - JDK 18 (March 2022)
>> - JDK 19 (September 2022)
>>
>> JDK 18[1] has entered Rampdown Phase Two (RDP2)[2]. Given that and to be
>> better prepared for the future, it makes sense to begin testing your
>> project(s) using early access (EA) builds of JDK 19[3]. Your feedback
>> allows us to evaluate and address issues you find while testing EA builds.
>>
>> This time, we have two heads-up to share:
>>
>> ## Heads-Up: JDK 18 - JEP 421 Deprecate Finalization for Removal
>>
>> Finalization is an outdated and brittle resource cleaning mechanism
>> present in the platform since, well, forever. Its use has been
>> discouraged for quite some time in favor of better alternatives (i.e.,
>> 'try with resources' and Cleaners). JEP 421 is another step towards the
>> removal of finalizers as it offers tools to investigate if a codebase is
>> still using finalization. To learn more, you should read JEP 421[4]. You
>> should also listen to the latest episode of the Inside Java Podcast[5]
>> dedicated to this topic. We encourage you to check if your project is
>> still using finalizers. If so, you should start to think about removing
>> them and rely instead on either 'try with resources' or Cleaners.
>>
>> ## Heads-Up: JVM does not flag constant class entries ending in '/'
>>
>> Prior to JDK 19, the JVM is loading classes (1) whose class file major
>> version is <49, i.e., before JDK 1.5, and (2) the class's name ends with
>> a '/'. This violates section 4.2.1 of the JVM specification [6] and is
>> addressed in JDK 19. In JDK 19, the JVM is throwing, for such classes, a
>> ClassFormatError exception as it already does with newer classes (JDK
>> 1.5+). Given that this issue affects only pre-JDK 1.5 classes, we expect
>> the compatibility risk to be very low.
>>
>> For more details, see JDK-8278448[7].
>>
>> [1] https://jdk.java.net/18/
>> 
>> [2]
>> https://mail.openjdk.java.net/pipermail/jdk-dev/2022-January/006361.html
>> [3] https://jdk.java.net/19/
>> 
>> [4] https://openjdk.java.net/jeps/421
>> [5] https://inside.java/podcast/21
>> 
>> [6]
>> https://docs.oracle.com/javase/specs/jvms/se17/html/jvms-4.html#jvms-4.2.1
>> [7] https://bugs.openjdk.java.net/browse/JDK-8278448
>>
>>
>> ## JDK 18
>>
>> JDK 18 is now in RDP2 (Rampdown Phase Two) with its feature set frozen a
>> few weeks back when it entered RDP1.
>>
>> ### JEPs integrated to JDK 18:
>>
>> - JEP 400: UTF-8 by Default
>> - JEP 408: Simple Web Server
>> - JEP 413: Code Snippets in Java API Documentation
>> - JEP 416: Reimplement Core Reflection with Method Handles
>> - JEP 417: Vector API (Third Incubator)
>> - JEP 418: Internet-Address Resolution SPI