[wildfly-dev] wildfly-10.0.0.Final and jdk9

[Tomaž Cerar]

All builds after b111 are jigsaw modulized JDK builds. There is no more
non-jigsaw jdk9 build.
Our CI currently uses b125 to test.

There are some known issues, mostly related to jigsaw issues
http://openjdk.java.net/projects/jigsaw/spec/issues/
We do have some issues also in our jira
https://issues.jboss.org/browse/WFCORE-1374 for core and
https://issues.jboss.org/browse/WFLY-3854 for full

Also as we now have code split in two, the most important part is
wildfly-core where we have our core runtime.
Which also has separate ci jobs, which look quite good atm
https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MasterLinuxJdk9

Google docs Dimitris shared, would be the good place to add extra issues or
any other observation.
You could also file issue in jira and assign it to David or me.

Just bit of heads up, the upcoming b126 will change names of new jigsaw
related parameters that gets passed to jvm.
As such, WildFly wont properly build and pass testsuite until we have code
updated.

--
tomaz


On Fri, Jul 8, 2016 at 5:02 AM, Scott Stark <sstark at redhat.com> wrote:

> I guess not as I got build 125 from https://jdk9.java.net/download/. I'll
> try https://jdk9.java.net/jigsaw/ instead.
>
> ----- Original Message -----
> From: "Stuart Douglas" <stuart.w.douglas at gmail.com>
> To: "Jason T. Greene" <jason.greene at redhat.com>
> Cc: "Scott Stark" <sstark at redhat.com>, wildfly-dev at lists.jboss.org
> Sent: Thursday, July 7, 2016 6:23:56 PM
> Subject: Re: [wildfly-dev] wildfly-10.0.0.Final and jdk9
>
> There are definitely still some issues (as can be seen from the CI
> failures), however it will boot.
>
> Stuart
>
> On Fri, Jul 8, 2016 at 11:00 AM, Jason T. Greene <jason.greene at redhat.com>
> wrote:
>
> > Is that the modular JDK build? IIRC there was still some issues there.
> Our
> > big challenge will be using jigsaw modules as part of a deployment of as
> a
> > library in the server.
> >
> > > On Jul 7, 2016, at 6:39 PM, Scott Stark <sstark at redhat.com> wrote:
> > >
> > > Ok, got the master branch running under jdk9. So is the issues list
> > given at the end of the Java 9 Problems & Solutions FAQ doc the best
> place
> > to pitch in?
> > >
> > > ----- Original Message -----
> > > From: "Stuart Douglas" <stuart.w.douglas at gmail.com>
> > > To: "Scott Stark" <sstark at redhat.com>
> > > Cc: wildfly-dev at lists.jboss.org
> > > Sent: Thursday, July 7, 2016 3:55:09 PM
> > > Subject: Re: [wildfly-dev] wildfly-10.0.0.Final and jdk9
> > >
> > > Wildfly upstream should be mostly working on JDK9:
> > >
> > > https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk9ea
> > >
> > > There is no released version that will work at the moment (and even if
> we
> > > did release a version that worked there is no guarantee it would
> continue
> > > to work past the next JDK9 ea release).
> > >
> > > Stuart
> > >
> > >> On Fri, Jul 8, 2016 at 7:17 AM, Scott Stark <sstark at redhat.com>
> wrote:
> > >>
> > >> I'm looking into the current state of issues around our CDI and JEE
> > >> containers and JDK9, and looking through the links that Dimitris sent
> me
> > >> regarding the issues we are tracking, I don't see a recipe for running
> > >> wildfly-10.0.0.Final, so I just gave it a try and see it is failing
> > early
> > >> on in several modules due to class instantiation.
> > >>
> > >> Is there a way to get wildfly booted under jdk9?
> > >>
> > >> What is the best way for me to help out getting these jdk9 issues
> > resolved?
> > > _______________________________________________
> > > wildfly-dev mailing list
> > > wildfly-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160708/ca15b479/attachment-0001.html