July 2018 - hibernate-dev - Jboss List Archives

[ehcache2] package name fix needed in 5.3.x documentation

by Laurent Almeras

Hi, Sorry to bother you on a deprecated feature subject, but I think the package names provided in documentation are broken : https://docs.jboss.org/hibernate/stable/orm/userguide/html_single/Hiberna... Do we agree that the correct names are org.hibernate.cache.ehcache.internal.SingletonEhCacheRegionFactory and org.hibernate.cache.ehcache.internal.EhCacheRegionFactory ? Not sure I'm right because of the .internal package; I spontaneously understand it as « private, do not touch » package. If I'm not wrong, I can open a Jira and propose a PR. -- Laurent Almeras

6 years, 5 months

2
4
0 / 0

Hibernate Validator 6.0.11.Final released

by Guillaume Smet

Hi, We just released Hibernate Validator 6.0.11.Final. The main goal of this release is to improve our compatibility with the upcoming JDK 11. It also contains a couple of bugfixes. More information here: http://in.relation.to/2018/07/18/hibernate-validator-6011-final-out/ Have a nice day. -- Guillaume

6 years, 5 months

1
0
0 / 0

Failing Analysis

by Alvaro Pedraza

Hi, I'm wondering if there is something wrong with LGTM Java analysis, because it has failed in my 2 open PR’s. https://github.com/hibernate/hibernate-orm/pull/2357 <https://github.com/hibernate/hibernate-orm/pull/2357> https://github.com/hibernate/hibernate-orm/pull/2433 <https://github.com/hibernate/hibernate-orm/pull/2433> Seeing the log in the first I got the message: [2018-07-15 15:50:19] [autobuild] [2018-07-15 15:50:19] [ERROR] Parsing error in file /opt/src/hibernate-core/src/test/java/org/hibernate/test/mappingexception/InvalidMapping.hbm.xml It seems to be a file to test mapping, so I assume there is something wrong with the analysis configuration as this file should not be analyzed at all, am I right? Besides, my changes don’t affect that code. Thanks in advance for your answers. Best regards: Alvaro E. Pedraza

6 years, 5 months

2
1
0 / 0

ORM - Migration guides: wiki or source repository?

by Guillaume Smet

Hi, I see that we have a migration-guide.adoc document in the repository: https://github.com/hibernate/hibernate-orm/blob/master/migration-guide.adoc and we also have migration guides in the wiki: https://github.com/hibernate/hibernate-orm/wiki/Migration-Guide---5.2 https://github.com/hibernate/hibernate-orm/wiki/Migration-Guide---5.3 Is there a reason why we have both? Lately, I updated the wiki one and I just noticed Gail updated the source one. So if we keep both, we will need to keep them in sync but I'm not sure there's any value in keeping both. Except having a migration guide bundled in the zip archive, maybe? Thoughts? Thanks! -- Guillaume

6 years, 5 months

3
4
0 / 0

Failing test for issue HHH-12688

by Alvaro Pedraza

Hi, working in something else I ran ./gradlew tests and exited with one failing test at org.hibernate.test.annotations.uniqueconstraint.UniqueConstraintBatchingTest I’ve been seeing https://hibernate.atlassian.net/browse/HHH-12688 <https://hibernate.atlassian.net/browse/HHH-12688> and it’s been closed and pushed, but the test is failing for me and just wanted to raise a flag just in case. Hope this helps. Best regards: Alvaro E. Pedraza

6 years, 5 months

2
2
0 / 0

NoORM IRC meeting minutes

by Guillaume Smet

Hi! Here are the minutes of our NoORM IRC meeting: 15:26 < jbott> Meeting ended Tue Jul 17 13:26:02 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 15:26 < jbott> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... 15:26 < jbott> Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... 15:26 < jbott> Log: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... -- Guillaume

6 years, 5 months

1
0
0 / 0

HHH-3138 - make constructor of DynamicMapEntityTuplizer public

by Alvaro Pedraza

Hi, I asigned myself this ticket and left a comment but unfortunately no feedback yet. https://hibernate.atlassian.net/browse/HHH-3138 This leads me to 2 questions: The first is the very same in the comment, which is if subclassing in DynamicMapEntityTuplizer is desirable? Please refer to the ticket for discussion The second is about what can I assume as a contributor. I mean, Is always the ticket a holy word (i.e. what the ticket says, should be done) or it is always debatable? I understand that I’m taking low priority tickets (because I’m almost a newbie contributor and I don’t feel like taking some more important ones) but how long should I wait to get some feedback in the comments? Thanks in advance for your answers. Best regards: Alvaro Pedraza

6 years, 5 months

4
4
0 / 0

JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

by Rory O'Donnell

Hi Sanne, *JDK 11 is in Rampdown Phase one* * *The overall feature set is frozen. No further JEPs will be targeted to this release.* * *Rampdown Phase two is scheduled to start * *26th of July* **JDK 11 EA build 22 , *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. *** * Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes *FOSS fixes in recent builds.* * JBoss Netty (b17) - JDK-8203937 (b17) * JUnit5 & other Foss Projects (b22) -JDK-8206355 **Notable changes in JDK 11 EA *build 22* * New Collection.toArray(IntFunction) Default Method (JDK-8060192 <http://bugs.openjdk.java.net/browse/JDK-8060192>) * Make some system properties effectively readonly (JDK-8066709 <http://bugs.openjdk.java.net/browse/JDK-8066709>) * Obsolete Support for Commercial Features (JDK-8202331 <http://bugs.openjdk.java.net/browse/JDK-8202331>) * JFR start failure after AppCDS archive created with JFR StartFlightRecording (JDK-8203664 <http://bugs.openjdk.java.net/browse/JDK-8203664>) * Change to policy for the default set of modules resolved when compiling or running code on the class path (JDK-8197532 <http://bugs.openjdk.java.net/browse/JDK-8197532>) *JDK 12 Early Access Build 02 is available at **http://jdk.java.net/12/* * OpenJDK builds 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>. * Changes in this build are listed here <http://hg.openjdk.java.net/jdk/jdk/log?revcount=10000&rev=reverse%28%22jd...> *The Quality Report for July 2018 is published **here <https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+for...>* * With the new six months release , we now publish the Quality report every three months. * Thanks to all the FOSS Projects for logging bugs against the JDK 11 EA Builds! Rgds,Rory [1] http://openjdk.java.net/projects/jdk/11/

6 years, 5 months

1
0
0 / 0

ORM - Asciidoclet

by Guillaume Smet

Hi, Are we using Asciidoc javadoc in the current tree (i.e. not 6)? With JDK 11, when ./gradlew :hibernate-core:javadoc is executed and this doclet is enabled, I have the following error: javadoc: error - invalid flag: -Xdoclint:none In the javadoc -X help, it says that doclint is "Provided by the Standard doclet". Removing the asciidoclet declaration fixes the issue. As asciidoclet is not enabled in the aggregateJavadocs task, I'm under the impression that it is not used. Could someone confirm this? Thanks! -- Guillaume

6 years, 5 months

2
7
0 / 0

[ORM] Javadoc errors fixing

by Guillaume Smet

Hi, So due to the issue with Asciidoclet I exposed in my previous email, I thought for some time that they had removed the -XDoclint flag in Java 11. Thus I started cleaning up all the Javadoc errors we have in the ORM source code... This led to the following changes: https://github.com/hibernate/hibernate-orm/compare/master...gsmet:HHH-128... . It's kinda huge and while it's only trivial changes, I'm a bit worried about what will happen when you will try to merge this in your 6 branch. All the errors are fixed except: - 3 reference not found errors for which I need advice - the errors in the generated sources that are thrown in the aggregateJavadocs task: the exclude rules are not taken into account by Gradle in this task, probably a Gradle bug, I saw an old forum post of Steve in the Gradle forum about this issue. Note: I don't have any issue if we consider it's not the right time to do that and we should only do that on 6. That's why I ask the question. I have no idea of what the 6 branch look like so I don't know how much of an issue it can be. Cherry-picking these changes on top of 6, once it's stabilized is a possibility. Thoughts? -- Guillaume

6 years, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev July 2018