Re: [wildfly-dev] Using a custom module to preview "next-gen" Hibernate versions on WildFly 9
On May 28, 2015, at 10:26 AM, Scott Marlow <smarlow(a)redhat.com>
wrote:
One issue for the Hibernate projects like Search, is that they need Hibernate 5 to be
included in WildFly, so they can start integrating with Hibernate 5 (with the
understanding that WildFly 10 will include Hibernate 5). Part of this effort of
integrating Hibernate 5, will be passing the various TCKs (from standalone JPA 2.1 TCK to
EE TCKs). Once we have some TCK runs with Hibernate 5, we will have a better idea of how
much work is remaining on the Hibernate ORM 5.x side.
From a scheduling point of view, I'm not sure what will be done by August. We can
either merge components changes in before they are known to pass all TCK tests or wait
until they are ready. Since we are short on time, I wanted to pass the TCK tests before
(merging Hibernate 5.0 into WildFly 10) but am flexible on that if the schedule could be
flexible also.
I liked your idea on HipChat. You could create a JPA branch and get it far enough along to
run the JPA tck tests on it, and in the meantime everyone could fork that branch as needed
for their development branches. Once we get promising looking results the branch can be
converted into one or more PRs.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat