Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

In this thread, Nicolas De Loof writes:

I solved the issue of compiling the application code for Java 1.3 AND
using java5 for tests :

Application code is compiled based on java 1.3 using compiler
bootclasspath argument.

Tests are compiled by adding a compiler execution prior to test-phase
(as I didn't find a way to configure testCompile to use a != configuration).

Here is my POM :


Please note this is only a maven2 hack. Tests are compiled prior to the "test-compile" phase to allow compiler configuration substitution. A better solution should be to have support for separate configuration of the compiler plugin for compile and test-compile phases.

Handy Hint


If you have to set more than one jar in your bootClasspath you need to separate them according to your platform (';' on Windows and ':' on Unix). The simplest way to support multi-plateform environment is to use ${path.separator} so you would have for example :

  • No labels