[jbosstools-dev] Should we build JBT 4.2 with JDK 7?

[Brian Fitzpatrick]

I we need to shift WS to build in JDK 7, that's fine. I'm honestly not sure of the need for JDK 5/6 support except for possibly runtime support back to JBoss AS 4.2. 

Open to suggestions. :)

I'm working on the WS test failures now - been chatting with Alessio today and hopefully we can figure out what's going on and get it fixed finally.

--Fitz

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Nick Boldt" <nboldt at redhat.com>
To: jbosstools-dev at lists.jboss.org
Sent: Tuesday, December 10, 2013 11:18:11 AM
Subject: [jbosstools-dev] Should we build JBT 4.2 with JDK 7?

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 at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev