Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<p>In <a href="http://www.nabble.com/-solved--product-codes-at-java-1.4%2C-test-sources-at-java-1.5-t2233884.html">this thread</a>, Nicolas De Loof writes:</p>

<p>I solved the issue of compiling the application code for Java 1.3 AND<br />
using java5 for tests :</p>

<p>Application code is compiled based on java 1.3 using compiler<br />
bootclasspath argument.</p>

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

<p>Here is my POM :</p>
<table class="wysiwyg-macro" data-macro-name="noformat" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e25vZm9ybWF0fQ&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>
&lt;plugin>
               &lt;groupId>org.apache.maven.plugins&lt;/groupId>
               &lt;artifactId>maven-compiler-plugin&lt;/artifactId>
               &lt;configuration>
                   &lt;source>1.3&lt;/source>
                   &lt;target>1.3&lt;/target>
                   &lt;compilerArguments>
                       &lt;bootclasspath>${settings.localRepository}/com/sun/rt/1.3.1_08/rt-1.3.1_08.jar&lt;/bootclasspath>
                   &lt;/compilerArguments>
               &lt;/configuration>
               &lt;executions>
                   &lt;execution>
                       &lt;id>compile-tests&lt;/id>
                       &lt;phase>process-test-sources&lt;/phase>
                       &lt;goals>
                           &lt;goal>testCompile&lt;/goal>
                       &lt;/goals>
                       &lt;configuration>
                           &lt;source>1.5&lt;/source>
                           &lt;target>1.5&lt;/target>
                           &lt;compilerArguments>
                               &lt;bootclasspath>
                                   ${java.home}/lib/rt.jar
                               &lt;/bootclasspath>
                           &lt;/compilerArguments>
                       &lt;/configuration>
                   &lt;/execution>
               &lt;/executions>
               &lt;dependencies>
                   &lt;dependency>
                       &lt;groupId>com.sun&lt;/groupId>
                       &lt;artifactId>rt&lt;/artifactId>
                       &lt;version>1.3.1_08&lt;/version>
                   &lt;/dependency>
               &lt;/dependencies>
           &lt;/plugin>
</pre></td></tr></table>
<p>Please note this is only a maven2 hack. Tests are compiled prior to the &quot;test-compile&quot; 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. </p>
<table class="wysiwyg-macro" data-macro-name="tip" data-macro-parameters="title=Handy Hint" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e3RpcDp0aXRsZT1IYW5keSBIaW50fQ&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="RICH_TEXT"><tr><td class="wysiwyg-macro-body">

<p>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 :</p>
<table class="wysiwyg-macro" data-macro-name="noformat" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e25vZm9ybWF0fQ&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>
&lt;bootclasspath>${settings.localRepository}/com/sun/rt/1.4.2_13/rt-1.4.2_13.jar${path.separator}${java.home}/lib/jsse.jar${path.separator}${java.home}/lib/jce.jar&lt;/bootclasspath>
</pre></td></tr></table></td></tr></table>
<p>In this thread:</p>

<p><a href="http://mail-archives.apache.org/mod_mbox/maven-users/200702.mbox/%3C8770432.post@talk.nabble.com%3E">http://mail-archives.apache.org/mod_mbox/maven-users/200702.mbox/%3C8770432.post@talk.nabble.com%3E</a></p>

<p>James Wiltshire found a way to obtain the desired result without needing to specify the bootclasspath.</p>

<p>An example that has source and target at 1.4 and 1.5 for production and test source, respectively:</p>
<table class="wysiwyg-macro" data-macro-name="noformat" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e25vZm9ybWF0fQ&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>
    &lt;build>
        &lt;plugins>
            &lt;plugin>
                &lt;groupId>org.apache.maven.plugins&lt;/groupId>
                &lt;artifactId>maven-compiler-plugin&lt;/artifactId>
                &lt;executions>
                    &lt;execution>
                        &lt;id>java-1.4-compile&lt;/id>
                        &lt;phase>compile&lt;/phase>
                        &lt;goals>
                            &lt;goal>compile&lt;/goal>
                        &lt;/goals>
                        &lt;configuration>
                            &lt;source>1.4&lt;/source>
                            &lt;target>1.4&lt;/target>
                        &lt;/configuration>
                    &lt;/execution>
                    &lt;execution>
                        &lt;id>java-1.5-compile&lt;/id>
                        &lt;phase>process-test-sources&lt;/phase>
                        &lt;goals>
                            &lt;goal>testCompile&lt;/goal>
                        &lt;/goals>
                        &lt;configuration>
                            &lt;source>1.5&lt;/source>
                            &lt;target>1.5&lt;/target>
                        &lt;/configuration>
                    &lt;/execution>
                &lt;/executions>
            &lt;/plugin>
        &lt;/plugins>
    &lt;/build>
</pre></td></tr></table>

<p>The above example is known to work with Maven 2.0.9.</p>