Message-ID: <1603419708.12899.1416797645951.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12898_1537334395.1416797645950" ------=_Part_12898_1537334395.1416797645950 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In this thread, Nicolas De Loof writes:=20
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
boot= classpath 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 !=3D configur= ation).
Here is my POM :=20 =20
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.=20 =20
In this thread:=20
James Wiltshire found a way to obtain the desired result without needing= to specify the bootclasspath.=20
An example that has source and target at 1.4 and 1.5 for production and = test source, respectively:=20 =20
The above example is known to work with Maven 2.0.9.