12:18 p.m.
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
12:23 p.m.
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(a)redhat.com>
To: jbosstools-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4:51 a.m.
On 10 Dec 2013, at 19:23, Brian Fitzpatrick <bfitzpat(a)redhat.com> wrote:
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.
Do we still run the generation via the server provided scripts and in an external process
? Then this would continue to work.
If we run it in “in-process” of eclipse, then yeah - that could be a problem but doesn’t
the WS generation supporting targeting different versions of the spec ?
/max
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(a)redhat.com>
To: jbosstools-dev(a)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(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
3:08 a.m.
It would somehow make sense to follow the move of Eclipse packages:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=423734 . They're still
using Java 6, but they discuss/plan to set Java 7 as minimal version for
Luna.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4:54 a.m.
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
4022
days inactive
4031
days old
jbosstools-dev@lists.jboss.org
4 comments
4 participants
participants (4)
-
Brian Fitzpatrick -
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt