Forge is compiled against JDK 7 but it is fully Java 8 compatible.

> On 05/22/2015 03:49 PM, Max Rydahl Andersen wrote: > Hey, > > We are going to make Java 8 required for upcoming Beta1. > > To see what kind of reaction we will get on moving to Java 8. > > This does *not* mean you should add Java 8 features to the codebase. > > We will still compile with Java 7 where we can, as we might be > required to support Java 7 before GA. > > Thus don't get too excited - but at least be happy users > will run with a faster Java with better memory management! > > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Just FYI: If you DO introduce a Bundle-RequireExecutionEnvironment of JavaSE-1.8 into a plugin, please make sure you also update your Jenkins job accordingly.

--- (Lengthy explanation follows.) If BREE = JavaeSE-1.8, then you can't compile it & successfully run tests with JDK 7. Since Arquillian depends on Sapphire 9 [0], which requires JDK 8, now too Arquillian requires JDK 8 to build. Its jobs have been updated. [0] https://github.com/jbosstools/jbosstools-arquillian/commit/13932fd9b917aa... Note that anything that needs to INCLUDE these BREE=JavaSE-1.8 bundles must ALSO be built with JDK 8 or Tycho can't resolve the bundles at build time. I've updated the Arquillian, JBT aggregate, and JBDS jobs to use jdk1.8 instead of jdk1.7. — This commit [1] broke this build [2] but after updating the job config to use jdk1.8, it's back to blue [3]. [1] https://github.com/jbosstools/jbosstools-base/commit/700dbf9b166072d394c9... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=716 On 05/23/2015 04:01 AM, Max Rydahl Andersen wrote: > > >> Forge is compiled against JDK 7 but it is fully Java 8 compatible. > > Yes - not following what your point is here. That's how all parts of > JBDS 8 and JBoss tools 4.2.x was. It's also what jbds 9 will be for > now - but exploring if we must support java 7 or have to do tricks to > have only certain parts of jbds 8 require java 8. > > Such as arquillian and batch Java EE tooling. > > >>> On 05/22/2015 03:49 PM, Max Rydahl Andersen wrote: >>> Hey, >>> >>> We are going to make Java 8 required for upcoming Beta1. >>> >>> To see what kind of reaction we will get on moving to Java 8. >>> >>> This does *not* mean you should add Java 8 features to the >>> codebase. >>> >>> We will still compile with Java 7 where we can, as we might be >>> required to support Java 7 before GA. >>> >>> Thus don't get too excited - but at least be happy users >>> will run with a faster Java with better memory management! >>> >>> /max >>> http://about.me/maxandersen >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

Actually, I should clarify. Seems that the BUILD may be ok w/ a lower JDK than the BREE specifies, but Surefire TESTING will surely NOT fire with the lower one, because the lower runtime environment is not compatible. And any "installation-like" step (like installing plugins into an update site build) will likely fail too. But to your question, "how we can make the installation require Java 8, but not require it at build time?"... I counter: "Given JDK 8 is everywhere (RHEL6.6, 7.1, Fedora, Ubuntu, Windows8, OSX) why can't we just build with the new standard baseline? Why encourage people to build w/ the EOL'd JDK 7?"

N On 05/24/2015 01:51 AM, Max Rydahl Andersen wrote: > On 23 May 2015, at 18:10, Nick Boldt wrote: > >> Just FYI: >> >> If you DO introduce a Bundle-RequireExecutionEnvironment of >> JavaSE-1.8 >> into a plugin, please make sure you also update your Jenkins job >> accordingly. > > crap, then tycho got picky ;/ > > tycho shouldn't be limiting its build options based on runtime > execution > environments. > > if it is then the idea about changing foundation to require it to > just > make install fails on Java 7 was a Bad idea. > > Anyone with a better idea on how we can make the installation require > Java 8, but not require it at build time ? > > /max > >> --- >> >> (Lengthy explanation follows.) >> >> If BREE = JavaeSE-1.8, then you can't compile it & successfully run >> tests with JDK 7. >> >> Since Arquillian depends on Sapphire 9 [0], which requires JDK 8, >> now >> too Arquillian requires JDK 8 to build. Its jobs have been updated. >> >> [0] >> https://github.com/jbosstools/jbosstools-arquillian/commit/13932fd9b917aa... >> >> >> Note that anything that needs to INCLUDE these BREE=JavaSE-1.8 >> bundles >> must ALSO be built with JDK 8 or Tycho can't resolve the bundles at >> build time. I've updated the Arquillian, JBT aggregate, and JBDS >> jobs >> to use jdk1.8 instead of jdk1.7. >> >> — >> >> This commit [1] broke this build [2] but after updating the job >> config >> to use jdk1.8, it's back to blue [3]. >> >> [1] >> https://github.com/jbosstools/jbosstools-base/commit/700dbf9b166072d394c9... >> >> [2] >> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >> >> [3] >> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >> >=716 >> >> >> On 05/23/2015 04:01 AM, Max Rydahl Andersen wrote: >>> >>> >>>> Forge is compiled against JDK 7 but it is fully Java 8 compatible. >>> >>> Yes - not following what your point is here. That's how all parts >>> of >>> JBDS 8 and JBoss tools 4.2.x was. It's also what jbds 9 will be for >>> now - but exploring if we must support java 7 or have to do tricks >>> to >>> have only certain parts of jbds 8 require java 8. >>> >>> Such as arquillian and batch Java EE tooling. >>> >>> >>>>> On 05/22/2015 03:49 PM, Max Rydahl Andersen wrote: >>>>> Hey, >>>>> >>>>> We are going to make Java 8 required for upcoming Beta1. >>>>> >>>>> To see what kind of reaction we will get on moving to Java 8. >>>>> >>>>> This does *not* mean you should add Java 8 features to the >>>>> codebase. >>>>> >>>>> We will still compile with Java 7 where we can, as we might be >>>>> required to support Java 7 before GA. >>>>> >>>>> Thus don't get too excited - but at least be happy users >>>>> will run with a faster Java with better memory management! >>>>> >>>>> /max >>>>> http://about.me/maxandersen >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools & Dev Studio >> http://nick.divbyzero.com > > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com