[hibernate-dev] Re: JDK 23 RDP2 | Removal of the legacy COMPAT locale provider and more heads-up!

[Yoann Rodiere via hibernate-dev]

Hey David,

Thank you for the updates. Everything looking good on our end:

Hibernate ORM: Version 6.6 tested against JDK 23 (EA 33) / 24 (EA 7). No
problems to report.

Hibernate Validator: Version 9.0 tested against JDK 23 (EA 33) / 24 (EA 7).
No problems to report.

Hibernate Search: Version 7.2 tested against JDK 23 (EA 33) / 24 (EA 7). No
problems to report.

Hibernate Reactive: Version 2.3 tested against JDK 23 (EA 31) / 24 (EA 6).
No problems to report.

So I assume Locale/SecurityManager changes don't affect these versions of
Hibernate projects. SecurityManager support is going to get removed in
future Hibernate versions, at any rate.

Sanne has been looking into Leyden, but you may already be aware, as I
think he reached out already (reporting issues in particular).

Have a nice weekend,

Yoann
Hibernate team

On Mon, Jul 22, 2024 at 8:37 AM David Delabassee via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:

> Welcome to the OpenJDK Quality Outreach summer update.
>
> JDK 23 is now in Rampdown Phase Two [1], its overall feature has been
> frozen a few weeks ago. Per the JDK Release Process, we have now turned our
> focus to P1 and P2 bugs, which can be fixed with approval [2]. Late
> enhancements are still possible, with approval, but the bar is now
> extraordinarily high. That also means that the JDK 23 Initial Release
> Candidates are fast approaching, i.e., August 8th [3]! So, and in addition
> to testing your projects with the latest JDK 23 early-access builds, it is
> now a good time to start testing with the JDK 24 early-access builds.
>
> Make sure to also check the heads-up below as some are related to JDK 23
> and might have some impact, i.e., the first one being related to the
> eventual removal of the Security Manager and the second one discusses the
> removal of the legacy COMPAT locale provider.
>
> [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-July/009252.html
> [2] https://openjdk.org/jeps/3#rdp-2
> [3] https://openjdk.org/projects/jdk/23/
>
>
> ## Heads-up - JDK 23: Subject.getSubject API Requires Allowing the
> Security Manager
>
> In JDK 17 and as announced in JEP 411 [4], the Security Manager was
> deprecated for removal. As part of that change, several Security Manager
> APIs, such as `AccessControlContext`, were deprecated for removal. The
> `Subject::doAs` and `Subject::getSubject` APIs depend on Security Manager
> related APIs even though they do not require Security Manager to be
> installed to use them.
>
> As of JDK 23 [5], to help applications prepare for the eventual removal of
> the Security Manager, subject authorization and the Subject APIs' behavior
> depend on allowing the Security Manager:
> - If the system property `java.security.manager` is set on the command
> line to the empty string, a class name, or the value `allow` then there is
> no behavior change compared to previous releases.
> - If the system property `java.security.manager` is not set on the command
> line or has been set on the command line to the value `disallow`, invoking
> the `Subject.getSubject` method will throw `UnsupportedOperationException`.
>
> Yet, running an application with `-Djava.security.manager=allow` is a
> temporary workaround to keep older code working. Maintainers of code using
> `Subject.doAs` and `Subject.getSubject` are strongly encouraged to migrate
> it with utmost priority to the replacement APIs, `Subject.callAs` and
> `Subject.current`. Make sure to check [5] and [6] for additional details.
>
> The jdeprscan tool [7] scans a JAR file for usage of deprecated API
> elements and is helpful to find code using these methods. Additionally,
> consider migrating as soon as possible code that stores a `Subject` in an
> `AccessControlContext` and invokes `AccessController.doPrivileged` with
> that context. Such code will stop working when the Security Manager is
> removed.
>
> [4] https://openjdk.org/jeps/411
> [5] https://jdk.java.net/23/release-notes#b15
> [6] https://inside.java/2024/07/08/quality-heads-up/
> [7] https://dev.java/learn/jvm/tools/core/jdeprscan/
>
>
> ## Heads-up - JDK 23: Unicode / Removal of COMPAT Locale Provider
>
> ### A Quick History of Locale Data in the JDK
>
> Before the Unicode Consortium created the Common Locale Data Repository
> (CLDR) in 2003 to manage locale data, the JDK had to provide its own
> collection. It did so successfully and in JDK 8 supported about 160
> locales. To reduce maintenance effort, allow better interoperability
> between platforms, and improve locale data quality, the JDK started to move
> towards CLDR in 2014:
> - JDK 8 comes with two locale data providers, which can be selected with
> the system property java.locale.providers:
>. JRE/COMPAT for the JDK’s legacy data collection (default)
>. CLDR for the CLDR data
>. a custom locale provider can be implemented
> - JDK 9 picks CLDR by default
> - JDK 21 issues a warning on JRE/COMPAT
>
> There are plenty of minor and a few notable differences between 

[hibernate-dev] Re: Hibernate Governance Model

[Yoann Rodiere via hibernate-dev]

Hello everyone,

After a few iterations, we reached consensus and the pull request got
merged: https://github.com/hibernate/hibernate.org/pull/231

The governance model is now live on our website:
https://hibernate.org/community/governance/
... as well as a page listing team members – at least those who opted in on
GitHub: https://hibernate.org/community/team/

Thanks to everyone who took the time to review and comment.


Happy coding,
Yoann Rodière
Hibernate team


On Fri, Jan 17, 2025 at 12:15 PM Yoann Rodiere  wrote:

> Hey all,
>
> As the move to the Commonhaus Foundation is progressing, we need to start
> thinking about complying with the foundation's requirements. Fortunately,
> they are few, and they make a lot of sense.
>
> A particularly important requirement is to publish various policies [1].
> Most of these policies we already publish or can start publishing easily;
> e.g. the code of conduct can be copied verbatim from Commonhaus' own code
> of conduct. But we, at Hibernate, have one gaping hole: our governance
> model.
>
> We've been getting by for years with an "implicit" governance and
> decision-making model, and it worked great. But:
>
> 1. If we want to join Commonhaus, the list of current project leaders, as
> well as how they get their position, must be clear: they are responsible
> for compliance with Commonhaus requirements and need to sign paperwork.
> 2. Our move to Commonhaus is, among other reasons, intended to provide
> strong openness guarantees and to foster contribution. Both require clarity
> on how exactly decisions are made.
>
> So, *it's time to make our governance model explicit*. I submitted a pull
> request [2] taking inspiration from the Commonhaus template [3].
>
> *To anyone involved in a Hibernate project*, be it now or a long time
> ago, be it just for one commit or full-time for years: *please have a
> look*, comment if you disagree or find problems, and let us know if you
> agree, with an approving review or a thumbs-up reaction on the main
> description.
> This governance model can only make sense if all members agree with it,
> and commit to complying with it. Ultimately, the decision will be up to
> Hibernate team members, but the opinion/concerns of all contributors are
> very important.
>
> *The pull request: https://github.com/hibernate/hibernate.org/pull/231
> *
>
> Please keep the discussions on that pull request, that'll make things
> easier to follow.
>
> [1] https://github.com/commonhaus/foundation/blob/main/templates/README.md
> [2] https://github.com/hibernate/hibernate.org/pull/231
> [3]
> https://github.com/commonhaus/foundation/blob/main/templates/GOVERNANCE.md
>
> Thanks in advance,
>
> Yoann Rodière
> Hibernate team
>
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/VKQ55FU6KLAQ46GJPMZS3I2S5RZU4KHD/

[hibernate-dev] Hibernate Governance Model

[Yoann Rodiere via hibernate-dev]

Hey all,

As the move to the Commonhaus Foundation is progressing, we need to start
thinking about complying with the foundation's requirements. Fortunately,
they are few, and they make a lot of sense.

A particularly important requirement is to publish various policies [1].
Most of these policies we already publish or can start publishing easily;
e.g. the code of conduct can be copied verbatim from Commonhaus' own code
of conduct. But we, at Hibernate, have one gaping hole: our governance
model.

We've been getting by for years with an "implicit" governance and
decision-making model, and it worked great. But:

1. If we want to join Commonhaus, the list of current project leaders, as
well as how they get their position, must be clear: they are responsible
for compliance with Commonhaus requirements and need to sign paperwork.
2. Our move to Commonhaus is, among other reasons, intended to provide
strong openness guarantees and to foster contribution. Both require clarity
on how exactly decisions are made.

So, *it's time to make our governance model explicit*. I submitted a pull
request [2] taking inspiration from the Commonhaus template [3].

*To anyone involved in a Hibernate project*, be it now or a long time ago,
be it just for one commit or full-time for years: *please have a look*,
comment if you disagree or find problems, and let us know if you agree,
with an approving review or a thumbs-up reaction on the main description.
This governance model can only make sense if all members agree with it, and
commit to complying with it. Ultimately, the decision will be up to
Hibernate team members, but the opinion/concerns of all contributors are
very important.

*The pull request: https://github.com/hibernate/hibernate.org/pull/231
*

Please keep the discussions on that pull request, that'll make things
easier to follow.

[1] https://github.com/commonhaus/foundation/blob/main/templates/README.md
[2] https://github.com/hibernate/hibernate.org/pull/231
[3]
https://github.com/commonhaus/foundation/blob/main/templates/GOVERNANCE.md

Thanks in advance,

Yoann Rodière
Hibernate team
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/WMNJHAWAVAAJVWFWNBIJV2GNRMUHOIW2/

[hibernate-dev] Commonhaus representatives

[Yoann Rodiere via hibernate-dev]

Hey,

As you all know, at least from the discussion on adding a governance model
[1], Gavin King is our representative to Commonhaus Foundation.

In the interest of transparency, I wanted to let you know that I would take
on the role of "Secondary representative" [2] -- i.e. fallback contact, and
helping hand in particular during the current bootstrapping phase.

Of course if there's an objection, we can revisit this decision.

[1] https://github.com/hibernate/hibernate.org/pull/231
[2] https://github.com/commonhaus/foundation/pull/239


Yoann Rodière
Hibernate team
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/GMPUSM2MAGRYUUFPTLTH3EHOJE6NYTDD/

[hibernate-dev] Fwd: [quarkus-dev] Jandex 3.3

[Yoann Rodiere via hibernate-dev]

Hey,

FYI, indexes created by Jandex 3.3 cannot be read by Jandex 3.2 and earlier
(see below).

In practice, since we're mainly *consumers* of Jandex indexes, this
probably means we want to upgrade to Jandex 3.3 ASAP.

*If* there are places where we produce and publish Jandex indexes, those
should probably stick to 3.2 for the time being.

Cheers,

Yoann Rodière
Hibernate team


-- Forwarded message -
From: Ladislav Thon 
Date: Mon, Apr 7, 2025 at 3:50 PM
Subject: [quarkus-dev] Jandex 3.3
To: Quarkus Development mailing list 


Hi,

I've just released Jandex 3.3.0, see the release notes here:
https://smallrye.io/blog/jandex-3-3-0/

Why I'm writing this? This version increments the persistent index format
version, so indices produced by Jandex 3.3 will NOT be readable by previous
Jandex versions. Since the only thing added to the persistent index in this
version is the enclosing class in case of local/anonymous classes declared
in a static/instance/field initializer, which is not commonly needed, it is
probably best for most users to stay on previous index format (either by
staying on Jandex 3.2 or by explicitly configuring the format version).

Hope this helps avoiding yet another bunch of problems :-)

LT

-- 
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+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/quarkus-dev/CALbocOkB_2bMfFk4iAh0SSnVpxgHOt%2B0-FN09Lg%2BriUmV_vCuA%40mail.gmail.com

.
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/ALA7EORPP4IR7G7FVR7M2VGUSZ4RGHKO/

[hibernate-dev] New member - Luca Molteni

[Yoann Rodiere via hibernate-dev]

Hello,

Luca Molteni (lucamolteni [1] on GitHub, volothamp in CC) recently moved to
my team at Red hat, with the explicit purpose of having him work full-time
on Hibernate projects and their integrations in downstream projects.

Luca has made a contribution to Hibernate ORM in the past [2], but is
expected to do a lot more now. Recently he worked on a rather complex pull
request around the Hibernate extensions in Quarkus [3], which just got
merged.

Moving forward, he will need access to some repositories in the Hibernate
organization on GitHub.

Thus, I'm proposing to make Luca a member of the Hibernate organization --
in particular on GitHub.

This requires consensus as per our governance model [4]. All in favor?

[1] https://github.com/lucamolteni
[2]
https://github.com/hibernate/hibernate-orm/pulls?q=is%3Apr+author%3Alucamolteni
[3] https://github.com/quarkusio/quarkus/pull/44473
[4] https://hibernate.org/community/governance/#role-granting-revoking

Cheers,

Yoann Rodière
Hibernate team
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/Y2WXKVRPMR2ZGN7TWD2KCFKUYJTYNDSW/

[hibernate-dev] Re: New member - Luca Molteni

[Yoann Rodiere via hibernate-dev]

I sure hope Marco already is :]

Yoann Rodière

Principal Software Engineer, Middleware

Hibernate team architect

Red Hat 


On Fri, Apr 11, 2025 at 11:06 AM Andrea Boriero via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:

> I'm in favor of Marco being a member of the Hibernate org
> ___
> hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
> To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
> https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/E5LZT24K5FOE4CGK7OKLHVOQNN5DWPYR/
>
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/2FY3UIK6CXDHADUQNA6FL3MZ6KNOVXNW/

[hibernate-dev] Re: New member - Luca Molteni

[Yoann Rodiere via hibernate-dev]

Thanks for your answers. Since there seems to be no objection, I'll go
ahead and add Luca to the GitHub org.

Welcome, Luca!

Yoann Rodière
Hibernate team


On Fri, Apr 11, 2025 at 2:16 PM Jan Schatteman via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:

> +1
>
> On Fri, Apr 11, 2025 at 10:36 AM Yoann Rodiere via hibernate-dev <
> hibernate-dev@lists.jboss.org> wrote:
>
> > Hello,
> >
> > Luca Molteni (lucamolteni [1] on GitHub, volothamp in CC) recently moved
> to
> > my team at Red hat, with the explicit purpose of having him work
> full-time
> > on Hibernate projects and their integrations in downstream projects.
> >
> > Luca has made a contribution to Hibernate ORM in the past [2], but is
> > expected to do a lot more now. Recently he worked on a rather complex
> pull
> > request around the Hibernate extensions in Quarkus [3], which just got
> > merged.
> >
> > Moving forward, he will need access to some repositories in the Hibernate
> > organization on GitHub.
> >
> > Thus, I'm proposing to make Luca a member of the Hibernate organization
> --
> > in particular on GitHub.
> >
> > This requires consensus as per our governance model [4]. All in favor?
> >
> > [1] https://github.com/lucamolteni
> > [2]
> >
> >
> https://github.com/hibernate/hibernate-orm/pulls?q=is%3Apr+author%3Alucamolteni
> > [3] https://github.com/quarkusio/quarkus/pull/44473
> > [4] https://hibernate.org/community/governance/#role-granting-revoking
> >
> > Cheers,
> >
> > Yoann Rodière
> > Hibernate team
> > ___
> > hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
> > To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
> > Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> > List Archives:
> >
> https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/Y2WXKVRPMR2ZGN7TWD2KCFKUYJTYNDSW/
> >
>
>
> --
>
> Jan Schatteman
>
> Red Hat <https://www.redhat.com/>
> <https://red.ht/sig>
> ___
> hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
> To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
> https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/7OHSYKODH4C6RD3DXH6FL2TXA4EQXJDW/
>
___
hibernate-dev mailing list -- hibernate-dev@lists.jboss.org
To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: 
https://lists.jboss.org/archives/list/hibernate-dev@lists.jboss.org/message/JMKC3SKGVLQTQJA7E3D32IA7K4NZKPDL/