I'd vote no. We've already done the core split for 9. I think adding another major change like this is a bad idea at this stage. On 02/09/2015 01:19 PM, Tomaž Cerar wrote: > Hi folks, > > we agreed that WildFly 10+ is going to require Java 8, given that its release date is > planned well after JDK7 will be EOL-ed. [1] > > Looking at all discussion and new projects / components already require JDK8 (Eltryon, new > WildFly client, Weld 3,...) for development. > I was wondering if we could move WildFly 9 to Java 8 as well? > > According to current release plan WF9 should be release around the same time JDK7 is > EOL-ed (April 2015) [1] > > Pros of moving to JDK8 early: > - components can use JDK8 eariler --> better testing > - supporting JDK9 will be easier (-XX:MaxPermSize fails to start JVM on 9) > - support for TLS SNI (think of it as virtual hosts for SSL) > - better ciphers and many other security related improvements > - nashorn (fast javascript engine) > - better concurrency libs > - easier testing, one less JDK combo to test on CI > > and of course all of the language improvements, lambda ftw! > > Cons of moving early > > - back porting of code could be impaired > - there is currently no non beta release of IBM JDK8 > > There are probably other pros & cons but in general I think it would be better to upgrade > early as there will be many > hidden issues with new Java 8 features people want to use but are server doesn't > understand currently, mostly here > are features like enhanced type annotations and default methods. > > This problem are and will creep up more and more often as adoption of Java 8 is quite good > already [2] and still rising. > > so what do you guys think? Should we move for WildFly or should we wait for 10 as planned? > > -- > tomaz > > > [1] http://www.oracle.com/technetwork/java/eol-135779.html > [2] http://jaxenter.com/java-2-111936.html > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- James R. Perkins JBoss by Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Tue, Feb 10, 2015 at 2:20 PM, Dimitris Andreadis <dandread(a)redhat.com <mailto:dandread@redhat.com>> wrote: There is also the TCK that would have to re-pass with jdk8. Absolutely, but AFAIR, we got tck update that works on Java 8.

Scott, can you confirm this?

_______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Tue, Feb 10, 2015 at 10:52 PM, Scott Marlow <smarlow(a)redhat.com <mailto:smarlow@redhat.com>> wrote: The Java 8 TCK update is for EE 6, not EE 7. The EE 7 TCK might also pass with Java 8 (we should try that independent of which Java version we require). Aha, this is what i was interested in. Any chance you can try with JDK8 against current master? Scott, can you confirm this? >From the EE 7 platform specification: " EE.9.5 Requirements for All Java EE Profiles The Java Platform, Standard Edition 7 is the required foundation for any Java EE 7 profile. Yes, but that doesn't say that is the only version that is required. *EE.2.4.1 Container Requirements* "This specification requires that containers provide a Java Compatible™ runtime environment, as defined by the Java Platform, Standard Edition, v7 specification (Java SE)." Which means any Java runtime that is compatible with v7 is fine, and as far as we know 8 is backward compatible, as it provides all v7 does and more. _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Tue, Feb 10, 2015 at 10:52 PM, Scott Marlow <smarlow(a)redhat.com <mailto:smarlow@redhat.com>> wrote: The Java 8 TCK update is for EE 6, not EE 7. The EE 7 TCK might also pass with Java 8 (we should try that independent of which Java version we require). Aha, this is what i was interested in. Any chance you can try with JDK8 against current master?

Scott, can you confirm this? >From the EE 7 platform specification: " EE.9.5 Requirements for All Java EE Profiles The Java Platform, Standard Edition 7 is the required foundation for any Java EE 7 profile. Yes, but that doesn't say that is the only version that is required. *EE.2.4.1 Container Requirements* "This specification requires that containers provide a Java Compatible™ runtime environment, as defined by the Java Platform, Standard Edition, v7 specification (Java SE)." Which means any Java runtime that is compatible with v7 is fine, and as far as we know 8 is backward compatible, as it provides all v7 does and more.

_______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Mabe this could help… javac -source 1.7 -target 1.7 -bootclasspath /usr/lib/jvm/java-7-oracle/jre/lib/rt.jar

On Feb 11, 2015, at 6:15 PM, Jason T. Greene <jason.greene(a)redhat.com&gt; wrote: I don't understand the hurry. > On Feb 9, 2015, at 3:20 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: > > Hi folks, > > we agreed that WildFly 10+ is going to require Java 8, given that its release date is planned well after JDK7 will be EOL-ed. [1] > > Looking at all discussion and new projects / components already require JDK8 (Eltryon, new WildFly client, Weld 3,...) for development. > I was wondering if we could move WildFly 9 to Java 8 as well? > > According to current release plan WF9 should be release around the same time JDK7 is EOL-ed (April 2015) [1] > > Pros of moving to JDK8 early: > - components can use JDK8 eariler --> better testing > - supporting JDK9 will be easier (-XX:MaxPermSize fails to start JVM on 9) > - support for TLS SNI (think of it as virtual hosts for SSL) > - better ciphers and many other security related improvements > - nashorn (fast javascript engine) > - better concurrency libs > - easier testing, one less JDK combo to test on CI > > and of course all of the language improvements, lambda ftw! > > Cons of moving early > > - back porting of code could be impaired > - there is currently no non beta release of IBM JDK8 > > There are probably other pros & cons but in general I think it would be better to upgrade early as there will be many > hidden issues with new Java 8 features people want to use but are server doesn't understand currently, mostly here > are features like enhanced type annotations and default methods. > > This problem are and will creep up more and more often as adoption of Java 8 is quite good already [2] and still rising. > > so what do you guys think? Should we move for WildFly or should we wait for 10 as planned? > > -- > tomaz > > > [1] http://www.oracle.com/technetwork/java/eol-135779.html > [2] http://jaxenter.com/java-2-111936.html > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Feb 12, 2015, at 3:06 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: That won't really change much, we could do that now and there wouldn't be any issues. Thing is that our testsuite won't catch anything more as our testsuite will still be using JDK7 features and as such wont really test how server behaves when JDK8 lang/jdk features are in use in deployments.

I guess first step would be to move PR processing to JDK8 while still use JDK7 for master & master-ignore On Thu, Feb 12, 2015 at 4:26 PM, Jason T. Greene <jason.greene(a)redhat.com&gt; wrote: Why don't we start with just moving the PR testing stuff to 8? And then have a one off 7 run. Sent from my iPhone On Feb 11, 2015, at 6:15 PM, Jason T. Greene <jason.greene(a)redhat.com&gt; wrote: > I don't understand the hurry. > > On Feb 9, 2015, at 3:20 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: > >> Hi folks, >> >> we agreed that WildFly 10+ is going to require Java 8, given that its release date is planned well after JDK7 will be EOL-ed. [1] >> >> Looking at all discussion and new projects / components already require JDK8 (Eltryon, new WildFly client, Weld 3,...) for development. >> I was wondering if we could move WildFly 9 to Java 8 as well? >> >> According to current release plan WF9 should be release around the same time JDK7 is EOL-ed (April 2015) [1] >> >> Pros of moving to JDK8 early: >> - components can use JDK8 eariler --> better testing >> - supporting JDK9 will be easier (-XX:MaxPermSize fails to start JVM on 9) >> - support for TLS SNI (think of it as virtual hosts for SSL) >> - better ciphers and many other security related improvements >> - nashorn (fast javascript engine) >> - better concurrency libs >> - easier testing, one less JDK combo to test on CI >> >> and of course all of the language improvements, lambda ftw! >> >> Cons of moving early >> >> - back porting of code could be impaired >> - there is currently no non beta release of IBM JDK8 >> >> There are probably other pros & cons but in general I think it would be better to upgrade early as there will be many >> hidden issues with new Java 8 features people want to use but are server doesn't understand currently, mostly here >> are features like enhanced type annotations and default methods. >> >> This problem are and will creep up more and more often as adoption of Java 8 is quite good already [2] and still rising. >> >> so what do you guys think? Should we move for WildFly or should we wait for 10 as planned? >> >> -- >> tomaz >> >> >> [1] http://www.oracle.com/technetwork/java/eol-135779.html >> [2] http://jaxenter.com/java-2-111936.html >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev