Thanks Steve! for reference JIRA and PR: - https://hibernate.atlassian.net/browse/HHH-11950 - https://github.com/hibernate/hibernate-orm/pull/1994
I also just noticed that supporting only the latest is consistent with the expectations we set in the documentation. Thanks, Sanne On 27 August 2017 at 17:06, Steve Ebersole <st...@hibernate.org> wrote: > I personally agree that we should only be maintaining a single slice of the > version matrix here... a given ORM version against the latest Wildfly > version. > > > On Sun, Aug 27, 2017, 7:31 AM Sanne Grinovero <sa...@hibernate.org> wrote: >> >> Hi all, >> >> WildFly 11 is coming: the version 11.0.0.CR1 was just released last week. >> >> The jipijapa integration point is slightly different. >> >> It shouldn't be hard to patch the current ORM build for this, but I'm >> wondering if we just want to update the target WF version, or start >> producing sets for both WildFly 10 and WildFly 11 ? >> >> Personally as soon as we can move all integration tests to WildFly 11, >> I won't be interested in maintaining WF10 compatibility for the 5.2 >> branch of Hibernate ORM (and related projects) so I'd be inclined to >> simply update the WF version. >> >> The motivations: >> - people are asking already for ORM modulesets for WF11 >> - these modules missing are a blocker for producing modulests for out >> other projects, e.g. Hibernate Search >> - people are asking for latest Hibernate Search modulesets for WF11 as >> well.. >> >> I'd treat this with urgency: while I don't expect any compatibility >> issue with WF11 it would be nice to be able to test it all before it's >> released as .Final >> >> Thanks, >> Sanne >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
