New CI machine preview
by Sanne Grinovero
You're all welcome to play with http://54.225.162.168/
however please keep these in mind:
- it's not the final machine: don't put too much effort in creating
nice build scripts as we'll reset it to clean state soon. We *might*
be able to store jobs defined so far, but we might choose not to.
- domain name should be coming: ci.hibernate.org ..not sure when, got
no replies so far from.
- authentication: just click on login, it will use OAuth2 to request
your identity via your GitHub account. Permissions to create new jobs,
edit existing jobs, run a build manually depend on your github account
be part of the Hibernate organization (or not, in which case you have
read only status)
At this stage I'd like to get a feeling if the hardware is powerful
enough, and also we need to select which other plugins we want to use,
I'm looking especially to:
- static analysis reports
- pull requests integration
both are relatively undefined, we can of course start simple and
improve later.. just checking this fits basic needs now.
Sanne
1 day, 3 hours
JDK 14 - Early Access build 19 is available
by Rory O'Donnell
Hi Sanne,
*OpenJDK builds - JDK 14 *- Early Access build 19 is available at
http://jdk.java.net/14/
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>.
* Release notes
o https://jdk.java.net/14/release-notes
* JEPs targeted to JDK 14, so far
o 352 - Non-Volatile Mapped Byte Buffers
<https://openjdk.java.net/jeps/352>
o 358 - Helpful NullPointerExceptions
<http://openjdk.java.net/jeps/358>
o 349 - JFR Event Streaming <https://openjdk.java.net/jeps/349>
* *I want to draw your attention to some notable changes in previous
builds of JDK 14.*
o *Build 14* - Classes are now loaded and linked by
Class.forName() (JDK-8212117
<https://bugs.openjdk.java.net/browse/JDK-8212117>)
+ we need help testing changes to 3-arg Class.forName method.
The method has always been specified to link the class but
the implementation has historically not done this when
invoked with the "initialize" parameter set to false. The
bug has been fixed in JDK 14 but it has the potential to
change the behavior of code that uses Class.forName to load
classes that cannot be linked.
* Changes in this build
<https://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B18%22%3...>
*Openjdk Builds - JDK 13.0.1 *General Availability -
https://jdk.java.net/13/
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>.
* Release notes <https://jdk.java.net/13/release-notes>
* Changes in this release
<https://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13.0.1%2B8%2...>
*Crypto roadmap updated* -
https://www.java.com/en/jre-jdk-cryptoroadmap.html
Targeted Date^(2) Targeted Release(s) Algorithm/Protocol Action How
to test/enable change Change Log
2019-10-15 13, 11, 8, 7 ECC on TLS Disable non-NIST Suite B EC curves
(sect283k1, sect283r1, sect409k1, sect409r1, sect571k1, sect571r1,
secp256k1) when negotiating TLS sessions Disabling non-NIST Suite B EC
curves when negotiating TLS sessions
<https://java.com/en/configure_crypto.html#DisablenonNIST> 2019-10-08
Announced.
Rgds,Rory
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
6 years
Narrowed HibernateProxy and Uninitialized bytecode-enhanced entities do not get detached
by Gail Badner
Hi,
I seem to remember this topic came when we were working on the
enhancement-as-proxy feature.
Basically, EnhancementAsProxyLazinessInterceptor#session does not get
nullified when the PersistenceContext gets cleared.
As a result, such an entity can still get initialized if
the SharedSessionContractImplementor is still open.
I also noticed that narrowed proxies are never added to the
PersistenceContext, but they still have a reference to
the SharedSessionContractImplementor from which the narrowed proxy
originated. These references never get nullified either.
I believe these are both bugs, and I would like to address them.
Please let me know if I'm missing something here.
Thanks,
Gail
6 years
HHH-13604 Define some Byteman rules to check what APIs are used at runtime: next steps?
by Fabio Massimo Ercoli
Hi guys,
the activity was very interesting, so I would like to thank Sanne who had
the idea and led the scope of the activity and thanks to Andrea who gave me
some nice ideas to improve the work.
With [this pull request](
https://github.com/hibernate/hibernate-orm/pull/3040) we have now rules to
check:
Read annotations
Class.forName
Other Java reflection APIs
Create proxy
Patter#compile
As a follow up (and probably it won’t be the only one) I created the issue:
https://hibernate.atlassian.net/browse/HHH-13669.
So far I’ve been involved in Hibernate OGM and Hibernate Search, so I don't
have a very deep knowledge of Hibernate ORM. So I would like to ask you:
what are the next steps?
And… is there something I can do to help?
Meanwhile I’ll be back to work on Hibernate Search. The integration with
Infinispan is still waiting…
Have a great weekend
Fabio
6 years
