similar to issue 501 - here is an example of the problem - on a multimodule
maven2 build, i have the top level project use my maven 2.0.6 installation and
set to use java 1.4.2 from websphere which is required to do this build.
Basically, the maven for this project needs to be executed with this
installation of java hence executing all the 1.4.2 goo (javac/rmic/etc). The
sub modules all use either the JAVA_HOME or the jdk tomcat is using instead of
the java set up in the top level project.

I have tried this with 1.104 snapshot after I saw 501 was resolved but this
problem persists.