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