<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=SL link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US>If hibernate 5.3 is ready and JPA 2.2 passes TCK, than we could probably bring it in.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Aa we do want to add more and more EE8 features, but only if they are ready.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>So if you feel that JPA 2.2 impl is ready than please go ahead and send PR for upgrade to 5.3 (given all other conditions for merging are met).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>But if you think you cannot get it done in about a month(more or less) than it would need to be postponed for WF13.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>And we need to consider what to do to make WF12 JPA impl work work on JDK9, aka upgrade the javasssit.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>--<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>tomaz<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:steve@hibernate.org">Steve Ebersole</a><br><b>Sent: </b>sreda, 06. december 2017 12:29<br><b>To: </b><a href="mailto:brian.stansberry@redhat.com">Brian Stansberry</a><br><b>Cc: </b><a href="mailto:jason.greene@redhat.com">Jason Greene</a>; <a href="mailto:tomaz.cerar@gmail.com">Tomaž Cerar</a>; <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br><b>Subject: </b>Re: [wildfly-dev] WildFly 11 and JDK9</p></div><p class=MsoNormal><o:p> </o:p></p><p>If y'all are willing to pull in Hibernate 5.3 the plan is to switch Hibernate to use ByteBuddy as It's default provider for byte code enhancement services rather than Javassist. </p><p>5.3 however is our JPA 2.2 (ee8) work, so that has to be factored into the decision. 2.2 adds some new classes that we do rely on code-wise - @TableGenerators and @SequenceGenerators. Because of this we cannot simply use 5.3 "under" the JPA 2.1 jar</p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Dec 5, 2017, 7:22 PM Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>There's a Javassist 3.22.0-GA out and we've moved on to WF 12 work. What are we going to do about this one?</p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We don't expect a long dev cycle for WF 12 so if we are going to make this change we shouldn't delay long. We don't want to try it and see right before the release. </p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Aug 31, 2017 at 10:24 AM, Steve Ebersole <<a href="mailto:steve@hibernate.org" target="_blank">steve@hibernate.org</a>> wrote:</p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>I guess we'd have to TIAS. Generally history tells us that these Javassist updates do not go smoothly for Hibernate/WF. However, at least part of purpose of this 3.22 release was for Hibernate and Java 9: <a href="https://issues.jboss.org/browse/JASSIST-261" target="_blank">https://issues.jboss.org/browse/JASSIST-261</a></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Back then I was able to use those 3.22 snapshots successfully, so hopefully this upgrade should go smoothly. But I agree that I would feel more comfortable with a Final rather than a CR.</p></div><div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal>On Thu, Aug 31, 2017 at 10:14 AM Jason Greene <<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal>I think its probably too late, but I think we can follow up with an 11.1 or 11.0.1 that includes Java 9 fixes. </p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I suspect we probably won’t have everything even if we did update Javassist (still some test failures etc).</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If someone has a strong argument otherwise, speak now or forever hold your peace!</p></div></div><div><div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Aug 31, 2017, at 8:21 AM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>> wrote:</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>Hey guys,</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>during development of WF11 we have done lots of work on making it build & run on JDK9.</p></div><div><p class=MsoNormal>as release nears I would like to summarize what the current state is and how to move on.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Currently most of our core [1] & full [2] testsuite passes on latest builds of JDK9.</p></div><div><p class=MsoNormal>Remaining failures are already addressed by [3] and [4]</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>**But** passing testsuite on JDK9 is not the same as using our binary distribution under JDK9.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Currently as part of running build / testsuite we override version of javassit to 3.22.0-CR2</p></div><div><p class=MsoNormal>which is currently the only version that works properly on JDK9.</p></div><div><p class=MsoNormal>As there is no .GA version of javassit that work on JDK9 avalible we currently do not have it as default.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>On top of that, hibernate as main user of javassit is not tested enough with this version of javassist</p></div><div><p class=MsoNormal>unless hibernate / JPA team says otherwise.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That would in practice mean that users running WF11 on JDK9 would have issues with JPA/Hibernate </p></div><div><p class=MsoNormal>based applications.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Currently I see two options how to address this:</p></div><div><p class=MsoNormal>- upgrade javassist to 3.22.x in server, preferably ask for .GA release.</p></div><div><p class=MsoNormal>- produce additional WildFly.x.x.x-jdk9 zip that would include the newer javassist.</p></div><div><p class=MsoNormal> </p></div><div><p class=MsoNormal>So question is do we even want to have working JDK9 build of WildFly 11 .Final</p></div><div><p class=MsoNormal>or should we postpone this for next update release.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--</p></div><div><p class=MsoNormal>tomaz</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[1] <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9" target="_blank">https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9</a> </p></div><div><p class=MsoNormal>[2] <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea" target="_blank">https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea</a> </p></div><div><p class=MsoNormal>[3] <a href="https://github.com/wildfly/wildfly-core/pull/2738" target="_blank">https://github.com/wildfly/wildfly-core/pull/2738</a> </p></div><div><p class=MsoNormal>[4] <a href="https://github.com/wildfly/wildfly-core/pull/2751" target="_blank">https://github.com/wildfly/wildfly-core/pull/2751</a> </p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>wildfly-dev mailing list<br><a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div><div><div><div><div><div><p class=MsoNormal><span style='color:black'>--<br>Jason T. Greene<br>Chief Architect, JBoss EAP<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Red Hat<o:p></o:p></span></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>wildfly-dev mailing list<br><a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></p></blockquote></div></div></div></div></div><p class=MsoNormal><br>_______________________________________________<br>wildfly-dev mailing list<br><a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></p></blockquote></div><p class=MsoNormal><br><br clear=all></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- </p></div><div><div><div><p class=MsoNormal>Brian Stansberry</p><div><p class=MsoNormal>Manager, Senior Principal Software Engineer</p></div></div></div></div></blockquote></div><p class=MsoNormal style='margin-left:4.8pt'>Red Hat</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>