<div dir="ltr">Just that. The pieces that allow us to plug in any version of Hibernate and any version of JPA (like 2.2 here recently) into WildFly for testing, without having to wait for WildFly to support everything else to have a release that includes the little bit we need</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Feb 22, 2018 at 9:48 AM Scott Marlow <<a href="mailto:smarlow@redhat.com">smarlow@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 02/22/2018 09:47 AM, Steve Ebersole wrote:<br>
> On Thu, Feb 22, 2018 at 7:44 AM Scott Marlow <<a href="mailto:smarlow@redhat.com" target="_blank">smarlow@redhat.com</a><br>
> <mailto:<a href="mailto:smarlow@redhat.com" target="_blank">smarlow@redhat.com</a>>> wrote:<br>
><br>
> On Thu, Feb 22, 2018 at 4:40 AM, Sanne Grinovero<br>
> <<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a> <mailto:<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a>>> wrote:<br>
><br>
><br>
> Scott: you remember we discussed including a JipiJapa adaptor<br>
> within the ORM codebase so that a matching version would be<br>
> released together? This would be a good time, so we include it,<br>
> want to help me with that?<br>
><br>
><br>
> Excellent, yes I want to help with that.<br>
><br>
><br>
> This would let us completely replace container-managed JPA support? If<br>
> so, that would be amazing<br>
<br>
I think that Sanne was only talking about the Hibernate ORM 5.3<br>
persistence provider modules and the JipiJapa module that integrates<br>
WildFly with ORM 5.3.<br>
<br>
Which other parts of container managed JPA support do you want to be<br>
able to replace?<br>
</blockquote></div>