------ Compiling Sources Using A Different JDK ------ Edwin Punzalan ------ 05 July 2006 ------ ~~ Copyright 2006 The Apache Software Foundation. ~~ ~~ Licensed under the Apache License, Version 2.0 (the "License"); ~~ you may not use this file except in compliance with the License. ~~ You may obtain a copy of the License at ~~ ~~ http://www.apache.org/licenses/LICENSE-2.0 ~~ ~~ Unless required by applicable law or agreed to in writing, software ~~ distributed under the License is distributed on an "AS IS" BASIS, ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ~~ See the License for the specific language governing permissions and ~~ limitations under the License. ~~ NOTE: For help with the syntax of this file, see: ~~ http://maven.apache.org/guides/mini/guide-apt-format.html Compiling Sources Using A Different JDK The <<>> parameter can be used to specify the version of the compiler that the plugin will use. However, you also need to set <<>> to <<>> for this to work. For example: +------- [...] [...] org.apache.maven.plugins maven-compiler-plugin true true 1.3 [...] [...] +------- To avoid hard-coding a filesystem path for the executable, you can use a property. For example: +------- ${JAVA_1_4_HOME}/bin/javac +------- Each developer then defines this property in {{{http://maven.apache.org/ref/current/maven-settings/settings.html}settings.xml}}, or sets an environment variable, so that the build remains portable. +------- [...] [...] compiler C:\Program Files\Java\j2sdk1.4.2_09 [...] compiler +------- If you build with a different JDK, you may want to {{{http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html} customize}} the jar file manifest.