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
When the compiler is forked, the jdk in the PATH is used, not the one
defined by JAVA_HOME.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
verbosetrue/verbose
forktrue/fork
/configuration
