<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">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. </div><div class=""><br class=""></div><div class="">I suspect we probably won’t have everything even if we did update Javassist (still some test failures etc).</div><div class=""><br class=""></div><div class="">If someone has a strong argument otherwise, speak now or forever hold your peace!</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 31, 2017, at 8:21 AM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com" class="">tomaz.cerar@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hey guys,</div><div class=""><br class=""></div><div class="">during development of WF11 we have done lots of work on making it build & run on JDK9.</div><div class="">as release nears I would like to summarize what the current state is and how to move on.</div><div class=""><br class=""></div><div class="">Currently most of our core [1] & full [2] testsuite passes on latest builds of JDK9.</div><div class="">Remaining failures are already addressed by [3] and [4]<br class=""></div><div class=""><br class=""></div><div class="">**But** passing testsuite on JDK9 is not the same as using our binary distribution under JDK9.</div><div class=""><br class=""></div><div class="">Currently as part of running build / testsuite we override version of javassit to 3.22.0-CR2</div><div class="">which is currently the only version that works properly on JDK9.</div><div class="">As there is no .GA version of javassit that work on JDK9 avalible we currently do not have it as default.</div><div class=""><br class=""></div><div class="">On top of that, hibernate as main user of javassit is not tested enough with this version of javassist</div><div class="">unless hibernate / JPA team says otherwise.</div><div class=""><br class=""></div><div class="">That would in practice mean that users running WF11 on JDK9 would have issues with JPA/Hibernate </div><div class="">based applications.</div><div class=""><br class=""></div><div class="">Currently I see two options how to address this:</div><div class="">- upgrade javassist to 3.22.x in server, preferably ask for .GA release.</div><div class="">- produce additional WildFly.x.x.x-jdk9 zip that would include the newer javassist.</div><div class=""> </div><div class="">So question is do we even want to have working JDK9 build of WildFly 11 .Final</div><div class="">or should we postpone this for next update release.</div><div class=""><br class=""></div><div class="">--</div><div class="">tomaz<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9" class="">https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9</a> </div><div class="">[2] <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea" class="">https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea</a> </div><div class="">[3] <a href="https://github.com/wildfly/wildfly-core/pull/2738" class="">https://github.com/wildfly/wildfly-core/pull/2738</a> </div><div class="">[4] <a href="https://github.com/wildfly/wildfly-core/pull/2751" class="">https://github.com/wildfly/wildfly-core/pull/2751</a> </div><div class=""><b class=""></b><i class=""></i><u class=""></u><sub class=""></sub><sup class=""></sup><strike class=""></strike><b class=""></b><i class=""></i><u class=""></u><sub class=""></sub><sup class=""></sup><strike class=""></strike><b class=""></b><i class=""></i><u class=""></u><sub class=""></sub><sup class=""></sup><strike class=""></strike><b class=""></b><i class=""></i><u class=""></u><sub class=""></sub><sup class=""></sup><strike class=""></strike><br class=""></div></div>
_______________________________________________<br class="">wildfly-dev mailing list<br class=""><a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">--<br class="">Jason T. Greene<br class="">Chief Architect, JBoss EAP</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Red Hat</div></div>
</div>
<br class=""></div></body></html>