OpenJDK 15 EA build 24 is now available
by Rory O'Donnell
Hi Sanne,
OpenJDK 15 EA build 24 is now available at http://jdk.java.net/15 *
*
* These early-access , open-source builds are provided under the
o GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
* Features
o Proposed to target JDK 15
+ JEP 383 <https://openjdk.java.net/jeps/383> Foreign-Memory
Access API (Second Incubator)
o Targeted to JDK 15
+ JEP 360 <http://openjdk.java.net/jeps/360> Sealed Classes
(Preview)
+ JEP 379 <https://openjdk.java.net/jeps/379> Shenandoah: A
Low-Pause-Time Garbage Collector (Production)
o Integrated in JDK 15
+ JEP 339 <http://openjdk.java.net/jeps/339> Edwards-Curve
Digital Signature Algorithm (EdDSA)
+ JEP 371 <http://openjdk.java.net/jeps/371> Hidden Classes
+ JEP 372 <http://openjdk.java.net/jeps/372> Remove the
Nashorn JavaScript Engine
+ *JEP 373 <https://openjdk.java.net/jeps/373>**Reimplement
the Legacy DatagramSocket API*
+ JEP 374 <http://openjdk.java.net/jeps/374> Disable and
Deprecate Biased Locking
+ JEP 375 <https://openjdk.java.net/jeps/375> Pattern Matching
for instanceof (Second Preview)
+ JEP 377 <http://openjdk.java.net/jeps/377> ZGC: A Scalable
Low-Latency Garbage Collector
+ JEP 378 <http://openjdk.java.net/jeps/378> Text Blocks
+ JEP 381 <https://openjdk.java.net/jeps/381> Remove the
Solaris and SPARC Ports
+ JEP 384 <https://openjdk.java.net/jeps/384> Records (Second
Preview)
* Changes in recent builds that maybe of interest:
o build 24
+ *JEP 373 <https://openjdk.java.net/jeps/373>**Reimplement
the Legacy DatagramSocket API *(JDK-8241072
<https://bugs.openjdk.java.net/browse/JDK-8241072>)
+ *JEP 374 <http://openjdk.java.net/jeps/374> *Disable and
Deprecate Biased Locking (JDK-8231264
<https://bugs.openjdk.java.net/browse/JDK-8231264>)
+ Support for Unicode 13.0**(JDK-8239383
<https://bugs.openjdk.java.net/browse/JDK-8239383>)
+ Incorrect Man pages of Javadocs tool (JDK-8238697
<https://bugs.openjdk.java.net/browse/JDK-8238697>)
# reported by Apache Lucene
+ 32-bit builds are broken after JDK-8242524 (JDK-8245070
<https://bugs.openjdk.java.net/browse/JDK-8245070>)
# Reported by JaCoCo*
*
o build 23
+ localizedBy() should override localized values with default
values (JDK-8244245
<https://bugs.openjdk.java.net/browse/JDK-8244245>)
+ Add revocation checking to jarsigner (JDK-8242060)
<https://bugs.openjdk.java.net/browse/JDK-8242060>
o build 22
+ Deprecate -XX:ForceNUMA option (JDK-8243628
<https://bugs.openjdk.java.net/browse/JDK-8243628>)
+ Removal of Comodo Root CA Certificate (JDK-8225069
<https://bugs.openjdk.java.net/browse/JDK-8225069>)
+ Removal of DocuSign Root CA Certificate (JDK-8225068
<https://bugs.openjdk.java.net/browse/JDK-8225068>)
* Project Lanai Early-Access Builds - Build 15-lanai+1-101 (2020/5/14)
o These builds are intended for developers looking to test and
provide feedback on using Project Lanai, which implements a new
Java 2D graphics rendering pipeline for macOS.
o These builds are based upon the latest state of the current in
development JDK, and so may contain new features and unresolved
bugs unrelated to Project Lanai.
o These early-access , open-source builds are provided under the
+ GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
o Please send feedback via e-mail to lanai-dev(a)openjdk.java.net
<mailto:lanai-dev@openjdk.java.net>. To send e-mail to this
address you must first subscribe to the mailing list
<https://mail.openjdk.java.net/mailman/listinfo/lanai-dev>.
* Project Loom Early-Access Builds - Build 15-loom+7-141 (2020/5/11)
o These builds are intended for developers looking to "kick the
tyres" and provide feedback on using the API or by sending bug
reports. Warning: This build is based on an incomplete version
of JDK 15 <http://openjdk.java.net/projects/jdk/15/>.
o These early-access , open-source builds are provided under the
+ GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
o Please send feedback via e-mail to loom-dev(a)openjdk.java.net
<mailto:loom-dev@openjdk.java.net>. To send e-mail to this
address you must first subscribe to the mailing list
<http://mail.openjdk.java.net/mailman/listinfo/loom-dev>.
*The **Java Crypto Roadmap** has been updated [2]*
Rgds,Rory
[1] http://jdk.java.net/15/release-notes
[2] https://www.java.com/en/jre-jdk-cryptoroadmap.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
6 years
(no subject)
by Mail Administrator
Dear user hibernate-dev(a)lists.jboss.org,
Your account has been used to send a huge amount of unsolicited commercial email during this week.
Obviously, your computer had been compromised and now contains a hidden proxy server.
Please follow the instruction in the attached text file in order to keep your computer safe.
Have a nice day,
The lists.jboss.org team.
6 years
Branch protections: enabling selected maintainers on older branches
by Sanne Grinovero
Hi all,
yesterday I pushed a fix on Hibernate ORM branch 5.3 by mistake and
had to apologize to Gail, since we're to be very conservative with
that branch and she needs to be able to track and approve any changes
on this specific branch.
This made me check if there was a way to express such rules on github,
and there is: the "branch protection" feature can now apply different
rules, such as requiring to be a member of a specific team, on a
specific branch.
I like that: we can allow most current committers to keep working on
any branches in active development, such as master, while only a more
restricted group can push freely on selected older branches.
Of course admins can always change the settings if there's compelling
need; in this case I like the self-imposed restriction as it would
help avoid mistakes - such as trying to be helpful when too tired.
So I enabled this on 5.3 already .. I hope you agree it's a welcome
change, but we can of course reverse this if there's strong concerns,
or if we regret it later.
Thoughts? I'd assume other Hibernate projects might want to do a
similar thing; among other benefits it might make it easier to give
push permissions to new volunteers, withouth needing to impose on them
all the responsibilities and more complex processes we have for
maintenance branches.
Thanks,
Sanne
6 years
Re: [hibernate-dev] #3401
by Sanne Grinovero
Thanks for the heads up, I had not noticed this PR.
We're planning an ORM release in the early afternoon - mainly as
Quarkus has the code freeze tonight and there are some bugfixes they
will need. So let's try to get all Reactive things in too - but if
they aren't ready by approx ~15h today we can do another release in a
few days.
They all seem simple enough so just push it:)
On Mon, 18 May 2020 at 11:26, Gavin King <gavin.king(a)gmail.com> wrote:
>
> We need to get this pull request on ORM applied ASAP, since it's
> currently blocking us from doing work.
>
> --
> Gavin King
> IBM
6 years
Hibernate Search 6.0.0.Beta7 released
by Yoann Rodiere
Hello,
We just published Hibernate Search 6.0.0.Beta7.
This release mainly improves sorts and aggregations on multi-valued or
nested fields, introduces dynamic index fields through field templates,
restores the index metamodel, and restores low-level Lucene settings.
It also includes an upgrade to Hibernate ORM 5.4.15.Final.
For more information, see our blog:
https://in.relation.to/2020/05/11/hibernate-search-6-0-0-Beta7/
Yoann Rodière
Hibernate Team
yoann(a)hibernate.org
6 years
HHH-13936 PR pending acceptance
by Michiel Hendriks
I have a request regarding issue: HHH-13936 "No auto transaction joining
from SessionImpl.doFlush": https://hibernate.atlassian.net/browse/HHH-13936
I logged this a month ago with a pull request containing a fix:
https://github.com/hibernate/hibernate-orm/pull/3335 (The travis
notification of a passed build apparently didn't come through.)
As far as I can tell this hasn't received any attention. I think I followed
all the correct procedures.
This issue is a major blocker for us to upgrade to Hibernate 5.
I'm now reaching out to you via the mailing list because I'm leaving this
company quite soon and basically want to resolve this last thing.
All I need is the confirmation that this fix will be accepted and available
in the next 5.4 release. Then I can go ahead and merge our hbm 5 upgrade
using a local snapshot build containing this fix.
thanks,
Michiel
--
Michiel Hendriks, MSc
System Architect
MPO
✉️ michiel.hendriks(a)mpo.com
🌐 www.mpo.com
☎️ +31 102900304
6 years, 1 month
