<div dir="ltr"><div><div><div><div><div>All builds after b111 are jigsaw modulized JDK builds. There is no more non-jigsaw jdk9 build.</div>Our CI currently uses b125 to test.</div><div><br></div>There are some known issues, mostly related to jigsaw issues <a href="http://openjdk.java.net/projects/jigsaw/spec/issues/">http://openjdk.java.net/projects/jigsaw/spec/issues/</a><br></div>We do have some issues also in our jira <br><a href="https://issues.jboss.org/browse/WFCORE-1374">https://issues.jboss.org/browse/WFCORE-1374</a> for core and<br><a href="https://issues.jboss.org/browse/WFLY-3854">https://issues.jboss.org/browse/WFLY-3854</a> for full<br><br></div>Also as we now have code split in two, the most important part is wildfly-core where we have our core runtime.<br></div>Which also has separate ci jobs, which look quite good atm <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9">https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9</a><br><div><div><div><div><br></div><div>Google docs Dimitris shared, would be the good place to add extra issues or any other observation.<br></div><div>You could also file issue in jira and assign it to David or me.<br><br></div><div>Just bit of heads up, the upcoming b126 will change names of new jigsaw related parameters that gets passed to jvm.<br></div><div>As such, WildFly wont properly build and pass testsuite until we have code updated.<br><br>--<br></div><div>tomaz<br></div><div><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 8, 2016 at 5:02 AM, Scott Stark <span dir="ltr"><<a href="mailto:sstark@redhat.com" target="_blank">sstark@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I guess not as I got build 125 from <a href="https://jdk9.java.net/download/" rel="noreferrer" target="_blank">https://jdk9.java.net/download/</a>. I'll try <a href="https://jdk9.java.net/jigsaw/" rel="noreferrer" target="_blank">https://jdk9.java.net/jigsaw/</a> instead.<br>
<span class="im HOEnZb"><br>
----- Original Message -----<br>
From: "Stuart Douglas" <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>><br>
</span><div class="HOEnZb"><div class="h5">To: "Jason T. Greene" <<a href="mailto:jason.greene@redhat.com">jason.greene@redhat.com</a>><br>
Cc: "Scott Stark" <<a href="mailto:sstark@redhat.com">sstark@redhat.com</a>>, <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
Sent: Thursday, July 7, 2016 6:23:56 PM<br>
Subject: Re: [wildfly-dev] wildfly-10.0.0.Final and jdk9<br>
<br>
There are definitely still some issues (as can be seen from the CI<br>
failures), however it will boot.<br>
<br>
Stuart<br>
<br>
On Fri, Jul 8, 2016 at 11:00 AM, Jason T. Greene <<a href="mailto:jason.greene@redhat.com">jason.greene@redhat.com</a>><br>
wrote:<br>
<br>
> Is that the modular JDK build? IIRC there was still some issues there. Our<br>
> big challenge will be using jigsaw modules as part of a deployment of as a<br>
> library in the server.<br>
><br>
> > On Jul 7, 2016, at 6:39 PM, Scott Stark <<a href="mailto:sstark@redhat.com">sstark@redhat.com</a>> wrote:<br>
> ><br>
> > Ok, got the master branch running under jdk9. So is the issues list<br>
> given at the end of the Java 9 Problems & Solutions FAQ doc the best place<br>
> to pitch in?<br>
> ><br>
> > ----- Original Message -----<br>
> > From: "Stuart Douglas" <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>><br>
> > To: "Scott Stark" <<a href="mailto:sstark@redhat.com">sstark@redhat.com</a>><br>
> > Cc: <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> > Sent: Thursday, July 7, 2016 3:55:09 PM<br>
> > Subject: Re: [wildfly-dev] wildfly-10.0.0.Final and jdk9<br>
> ><br>
> > Wildfly upstream should be mostly working on JDK9:<br>
> ><br>
> > <a href="https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea" rel="noreferrer" target="_blank">https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea</a><br>
> ><br>
> > There is no released version that will work at the moment (and even if we<br>
> > did release a version that worked there is no guarantee it would continue<br>
> > to work past the next JDK9 ea release).<br>
> ><br>
> > Stuart<br>
> ><br>
> >> On Fri, Jul 8, 2016 at 7:17 AM, Scott Stark <<a href="mailto:sstark@redhat.com">sstark@redhat.com</a>> wrote:<br>
> >><br>
> >> I'm looking into the current state of issues around our CDI and JEE<br>
> >> containers and JDK9, and looking through the links that Dimitris sent me<br>
> >> regarding the issues we are tracking, I don't see a recipe for running<br>
> >> wildfly-10.0.0.Final, so I just gave it a try and see it is failing<br>
> early<br>
> >> on in several modules due to class instantiation.<br>
> >><br>
> >> Is there a way to get wildfly booted under jdk9?<br>
> >><br>
> >> What is the best way for me to help out getting these jdk9 issues<br>
> resolved?<br>
> > _______________________________________________<br>
> > wildfly-dev mailing list<br>
> > <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>