Re: [hibernate-dev] ORM 5.1 vs compatibility with Java 6

Hi Sanne, I didn't notice the failures either. I've been running it with JAVA6_HOME pointing to jdk7, but I can't remember why I would have changed it to that. It sounds like 5.1 branch will be a product branch for a while, so if it's easy to make it compatible to JDK6, then I'd prefer to do

Re: [hibernate-dev] module org.hibernate.commons.annotations

+1 On Tue, Feb 13, 2018, 3:42 PM Sanne Grinovero wrote: > I'd like to release an Hibernate Commons Annotations version > 5.0.2.Final to declare its Jigsaw module name as an automatic module > name. Version 6 - whihch I proposed in a different thread - should > then use this

[hibernate-dev] module org.hibernate.commons.annotations

I'd like to release an Hibernate Commons Annotations version 5.0.2.Final to declare its Jigsaw module name as an automatic module name. Version 6 - whihch I proposed in a different thread - should then use this module but have a proper module definition. Is module name

[hibernate-dev] ORM 5.1 vs compatibility with Java 6

Is Hibernate ORM 5.1 still meant to be compatible with Java 6? The readme seems to promise that it should be, but it's not: I happened to try compiling it and it failed, as some recent changes are using JDK classes which have been introduced in 7. Turns out it builds fine for Andrea an Chris, as

[hibernate-dev] Hibernate OGM 5.3 CR1 released

HIbernate OGM 5.3 CR1 is ready! The major improvement was the version upgrade for Hibernate ORM (5.2.13.Final) and Hibernate Search (5.9.0.Final). The application of Clustered Counters, for Infinispan Embedded dialect, has been improved in this version. All the details in the blog post:

[hibernate-dev] NoORM IRC meeting minutes

Hi, Here are the minutes of our biweekly meeting: 16:01 < jbott> Meeting ended Tue Feb 13 15:01:26 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 16:01 < jbott> Minutes:

Re: [hibernate-dev] ORM CI jobs - erroneous github triggers

I can have a look at this issue. If you have any suggestions, let me know. Thanks On Tue, Feb 13, 2018 at 2:22 PM, Sanne Grinovero wrote: > Unfortunately we have to reopen this thread. The issue is affecting us > again (since some weeks I think) and in larger scale,

Re: [hibernate-dev] ORM CI jobs - erroneous github triggers

Unfortunately we have to reopen this thread. The issue is affecting us again (since some weeks I think) and in larger scale, affecting all builds. I guess it means the previous workaround is no longer effective after some of the recent Jenkins / plugins updates. On IRC we where wondering if we

Re: [hibernate-dev] Some insight about HHH-12101 / remove HQL-style positional parameters

Thanks for your feedback. As I currently use QueryDSL generated queries, it's not easy to switch the way my queries are generated. I post an issue with a github branch with some simple test-cases here: https://hibernate.atlassian.net/browse/HHH-12290 Laurent Almeras Le 07/02/2018 à 19:43,

[hibernate-dev] Jenkins Updates on Friday

Hi, I'm going to run some updates on Jenkins this Friday. They are minor updates and should be painless but you never know. Cheers, Davide ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

On Tue, Feb 13, 2018 at 11:59 AM, Yoann Rodiere wrote: > > - org.hibernate.search.jms-support > > Not sure it's a valid name (aren't hyphens forbidden in package names, and > aren't module names constrained by the same rules?), but apart from that it > looks good. Maybe

[hibernate-dev] HCANN 6

I'd like to push some updates to Hibernate Commons Annotations, looks like a good time to plan it as a 6.0 release to nicely align with plans of our other projects. I plan to: - bump its version to 6.0.0-SNAPSHOT - upgrade the Gradle build - upgrade its dependencies to latest (which means just

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

2018-02-13 11:04 GMT+01:00 Yoann Rodiere : > > How can you be sure of that though without trying it out? > > If what you meant by "work as modules" was "work as *automatic* modules" > (i.e. with dependencies in the classpath), we already test that. We just > happen to know

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

On 13 February 2018 at 08:44, Yoann Rodiere wrote: >> IMO automatic module names should only be declared after at least some > basic vetting that these modules will actually work when used as modules. > If that's not the case, I wouldn't add these headers, as users rightfully

[hibernate-dev] JDK 10: First Release Candidate - JDK 10 b43

Hi Sanne, *JDK 10 build 43 is our first JDK 10 Release Candidate [1]* * JDK 10 Early Access  build 43 is available at : - jdk.java.net/10/ Notable changes since previous email.** *build 43 * * JDK-8194764 - javac incorrectly flags

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

> How can you be sure of that though without trying it out? If what you meant by "work as modules" was "work as *automatic* modules" (i.e. with dependencies in the classpath), we already test that. We just happen to know they can't work as "full" modules (with module-info) yet. > If there are

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

2018-02-13 9:44 GMT+01:00 Yoann Rodiere : > > IMO automatic module names should only be declared after at least some > basic vetting that these modules will actually work when used as modules. > If that's not the case, I wouldn't add these headers, as users rightfully > may

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

2018-02-13 0:37 GMT+01:00 Sanne Grinovero : > The split package problem with Lucene won't easily go away, as we > can't upgrade Lucene now. > > But I vaguely remember working with you on that, didn't we figure out > that one of the Lucene modules wasn't essential? > The

Re: [hibernate-dev] HSEARCH-3000 Pick Jigsaw Automatic Module names for all published modules

> IMO automatic module names should only be declared after at least some basic vetting that these modules will actually work when used as modules. If that's not the case, I wouldn't add these headers, as users rightfully may consider their presence as endorsement of using them as modules. If I