Hello everyone, in a multimodule project i'm working on, a first module defines a new compilerId, intended to be used with the maven-compiler-plugin (see [1] for details). Some of the other submodules configure their pom the maven-compiler-plugin so that it should use the compilerId defined in the first module. Unfortunately, this configuration doesn't seem to work. Infact, when i issue a 'mvn install' from the root of the multi-module project, i get :
[INFO] No such compiler 'myCompilerId'. and the compilation process stops, just when it was entering into the first of the submodules using 'myCompilerId'. If instead I go into the module using 'myCompilerId' and manually issue "mvn install" from there, everything goes fine, as 'myCompilerId' gets resolved successfully. This is quite annoying, as it inhibits a 'single command' installation process. This jira issue http://jira.codehaus.org/browse/MCOMPILER-8 sounds very similar, if not the same: unfortunately, the suggested workaround (that is, specifying a runtime scope for the plexus-compiler-myCompilerId) hasn't produced a working result :-( Any idea ? thanks, valerio [1] http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html -- http://valerioschiavoni.blogspot.com http://jroller.com/vschiavoni --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
