JDK 12 enters Rampdown Phase One
by Rory O'Donnell
Hi Sanne,
*JDK 12 Early Access build **is now available **at : - jdk.java.net/12/*
* Per the JDK 12 schedule [1], we are now in Rampdown Phase One.
o For more details , see Mark Reinhold's email to jdk-dev mailing
list [2]
o The overall feature set is frozen, no further JEPs will be
targeted to this release.
o We’ve forked the main-line source repository, jdk/jdk, to the
JDK 12 stabilization repository.
Changes since the last availability email
*…
[View More] JEP 189: Shenandoah: A Low-Pause-Time Garbage Collector
(Experimental) <http://openjdk.java.net/jeps/189> moved to *Targeted*.
* JEP 334: JVM Constants API <http://openjdk.java.net/jeps/334> moved
to *Targeted*.
* JEP 344: Abortable Mixed Collections for G1
<http://openjdk.java.net/jeps/344> moved to *Targeted*.
* JEP 346: Promptly Return Unused Committed Memory from G1
<http://openjdk.java.net/jeps/346> to *Targeted*.
* JEP 326: Raw String Literals <https://openjdk.java.net/jeps/326>
(Preview) *Proposed to drop from JDK 12*
o link to proposal on jdk-dev
<https://mail.openjdk.java.net/pipermail/jdk-dev/2018-December/002402.html>
Bug fixes reported by Open Source Projects :
o JDK-8211051 - fixed in b22 - reported by JUnit5
o JDK-8211422 - fixed in b23 - reported by Apache Batik
The Java Crypto Roadmap <https://java.com/cryptoroadmap> has been
updated with the following target:
* With the 2019-04-16 CPU,
o Targeted Releases - JDK 12, JDK 11, JDK 8, and JDK 7
o Distrust TLS server certificates anchored by Symantec Root CAs.
Oracle Java SE 8 Release Updates [3]
* Public updates for Oracle Java SE 8 released after January 2019 will
not be available for business, commercial or production use without
a commercial license.
Rgds, Rory
[1] http://openjdk.java.net/projects/jdk/12/#Schedule
[2] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-December/002405.html
[3] https://java.com/en/download/release_notice.jsp
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
[View Less]
6 years, 3 months
Hibernate ORM 5.4.0.Final released
by Guillaume Smet
Hi,
We just released Hibernate ORM 5.4.0.Final after two candidate releases.
Thanks to everyone involved in testing the CRs, that was very helpful.
The idea behind 5.4 is to be a drop-in replacement of 5.3.x so please
consider moving to this version as 5.3.x will only receive critical
bugfixes.
You can find the full announcement on our blog:
http://in.relation.to/2018/12/12/hibernate-orm-540-final-out/ .
Have a nice day!
--
Guillaume
6 years, 3 months
Releasing ORM 5.4.0.Final tomorrow
by Guillaume Smet
Hi,
FYI, I will release ORM 5.4.0.Final tomorrow afternoon my time.
Please don't merge any last minute changes as I won't have the time to deal
with potential issues.
Thanks.
--
Guillaume
6 years, 3 months
Created a Jenkins job to publish Snapshot artifacts for ORM 6.0
by Yoann Rodiere
Hello,
Last time we discussed it, it seemed there wasn't any automatic job
regularly publishing ORM 6.0 snapshot artifacts; right now I can see that
the latest snapshot was published on December 5th by Steve himself (not
Jenkins); probably while performing tests for the 6.0.0.Alpha1 release?
So I just created a Jenkins job to publish Snapshot artifacts for ORM 6.0:
http://ci.hibernate.org/view/ORM/job/hibernate-orm-6.0-h2-main/
It's just a copy of hibernate-orm-master-h2-main with the …
[View More]branch changed to
wip/6.0 and a one-build-per-hour throttle added (we may remove that if you
want).
For now the job is disabled. Steve, do you agree with publishing snapshot
artifacts? Can I enable this job? Do I have to add specific options (ignore
some tests, some modules, ...) to the gradle command in order for the build
to pass? Do you want me to disable build failure notifications?
Snapshots would come in handy to test Hibernate Search 6.0 against ORM 6.0.
For now Search 6 is still using ORM 5.4, because a lot of Search's tests
need association types that are not yet supported in 6, but I'd like to
keep track of progress made on ORM 6 so I can react if further
incompatibilities arise.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
[View Less]
6 years, 3 months
6.0 Alpha1 prep
by Steve Ebersole
As I am preparing the Alpha1 release a few topics of discussion have come
up...
Previously (last year's f2f) we had decided to unify the artifact naming
conventions; specifically for ORM this meant renaming the groupId from
`org.hibernate` to `org.hibernate.orm` as part of 6.0. I wanted to see if
everyone still agrees with this.
There are a few artifacts we need to decide how to handle:
- `hibernate-entitymanager` and `hibernate-java8` have been part of
`hibernate-core` since 5.2 (I …
[View More]thought moving `hibernate-entitymanager`
happened way earlier, but seems like not). Should we drop these? They
have been defined as relocations for quite some time now).
- `hibernate-ehcache` defines support for using Ehcache 2 as a
second-level cache, which is a version the Ehcache team does not even
support anymore and have not for quite a few years. Ehcache 3 is a JCache
compliant version and the way that the Ehcache team prefer to handle the
integration (in fact they wrote most of `hibernate-jcache`). IMO this
should be removed as well. Thoughts?
- `hibernate-infinispan` - support for using Infinispan as a Hibernate
L2C has been moved to the Infinispan project. Again, IMO this module should
go away. Thoughts?
Andrea, Chris.. anything you can think of that I missed?
[View Less]
6 years, 3 months
