This is not a bug - if you want to specify a specific JVM to run, try using the <executable> element to specify a path. You can even use the ${ env.JAVA_HOME} variable, like ${env.JAVA_HOME}/bin/javac
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html On 6/28/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
When the compiler is forked, the jdk in the PATH is used, not the one defined by JAVA_HOME. <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <verbose>true</verbose> <fork>true</fork> </configuration> </plugin> Is this a bug? Paul Spencer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Eric Redmond http://www.sonatype.com