What I'd like to do is to execute tests in 1.5 and 1.6. Changing the rt.jar
is not enough. By the past we had trouble with bugs in JDK. Just changing
the rt.jar is not enough. We really need to use another JDK.
What I'd like to do is during the dev to use JDK 1.5, to release with the
JDK 1.5
The wiki page explain a solution I've found to compile for a target 1.3 Jre
with using another JRE to support dev tools, like some testing / mock tools
that require java5.
The goal is not to test under various JRE, just to assert the binaries will
not reference methods that do not exist under
Problem of using multiple server is that you rebuild the jar. Consequently
you do not test the jar compile in jdk 1.5 in Jdk 1.6.
I really like to test the jar build with jdk1.5 in jdk 1.6
nicolas de loof-2 wrote:
The wiki page explain a solution I've found to compile for a target 1.3
Jre
You should only run tests, not compile the jar, by packaging your tests as
test-jar and runing them in a portability-test project you can deploy on a
ci-server with various JRE.
Nico.
2007/2/19, JC Walmetz [EMAIL PROTECTED]:
Problem of using multiple server is that you rebuild the jar.
I have tried to do that. In a standard project surefire scans the test
classes directory to search for junit tests. When test cases are in a jar
file I do not find how to parameter surefire plugin to scan test-jar.
How can I parameter surefire to scan a test-jar ?
nicolas de loof-2 wrote:
You may look at the maven-dependecy-plugin and it'zs unpack goal
2007/2/19, JC Walmetz [EMAIL PROTECTED]:
I have tried to do that. In a standard project surefire scans the test
classes directory to search for junit tests. When test cases are in a jar
file I do not find how to parameter
This is discussed now and then on this list with various approaches
posted, so search the Archives.
Also, this is discussed in the Wiki:
http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Different+JDK+Versions
I have to imagine you could utilize various configurations in multiple
