Re: [jbosstools-dev] Should we build JBT 4.2 with JDK 7?
For now I say, keep the jdk build requirement as low as possible.
Don’t just raise it to JDK 7 without the component actually needing/wanting it.
That said - Java 7 is what we should be targeting for *running* JBT/JBDS since
it is actually starting to be hard to get Java 6 on some machines ;)
One downside of moving from Java 6 to 7 is though we loose the option of 32-bit JVM
on OSX which in turn means we cannot support the visual part of VPE on OSX anymore.
But since VPE uses xulrunner which looks like it can’t run on GTK3 anymore we
need to find another solution for that anyway.
/max
On 10 Dec 2013, at 19:18, Nick Boldt <nboldt(a)redhat.com> wrote:
Three of the projects in JBoss Tools use JDK 7 for testing: Server,
Webservices, and now Forge 2.
This is accomplished in Jenkins like this:
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m
-Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}"
-Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}"
-Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}"</jvmOptions>
But all the projects still use JDK 6 to compile.
<jdk>java16_default</jdk>
Is that OK? Or is it time to consider moving to JDK 7 for building as
well as running tests?
If this warrants a JIRA, please open one and link to it from here. If
not, discuss why it makes sense to stay with JDK 6 for compilation.
If your project needs JDK 7 to run tests, and is not listed above,
please open a JIRA or fix your _42 and _master jobs directly. If you
can't fix your job (not sure how or don't have permission), email me or
JIRA me and I'll fix your jobs for you.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev