On 7/29/11 9:36 AM, Jörg Schaible wrote: > Hi Phil, > > Phil Steitz wrote: > >> On 7/28/11 11:18 PM, Jörg Schaible wrote: >>> Jörg Schaible wrote: > [snip] > >>>> Use the java-1.4 profile (look into the commons parent) and define its >>>> home in your settings.xml: >>>> >>>> <profile> >>>> <id>java-1.4</id> >>>> <properties> >>>> <JAVA_1_4_HOME>/opt/blackdown- >>>> jdk-1.4.2.03</JAVA_1_4_HOME> >>>> </properties> >>>> </profile> >>>> >>>> You can use then any newer Java version to build. >>> Speak: You can use any newer Java version to run Maven, compilation and >>> running the test will use the Java version of the profile. >> Thanks! You said compilation and execution both, right? > Yes. > >> So >> Surefire is somehow smart enough to avoid using its own jdk 1.5+ >> stuff, or does it somehow launch a new JVM for each test? > New JVM. > >> Also, can >> the property to specified on the command line? > Sebb did most of it IIRC, see here http://commons.apache.org/commons-parent- > pom.html#Testing_with_different_Java_versions
Nice! Looks like you can even just use environment variables. I will do that next time. Thanks, guys! Phil > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
