Brian Fox wrote:
I guess what I had in mind was given a single reactor build:
A : Jar
B: War but binds jar to a phase.
Will B always get the same version of the jar plugin as A?
No, the projects are handled independently regarding their build plugins.
For instance, if B doesn't lock down the version of the JAR plugin it
will encounter auto resolution, while A could use a default version from
the lifecycle mapping for "jar" packaging.
In other words, running "mvn install" on B or A alone is equivalent to
running "mvn install" on the reactor build. Ignoring dependency
resolution, we made some efforts in Maven 3 to ensure projects build the
same regardless whether they run in a reactor or in isolation.
The lifecycle mapping gets merged into the effective POM for a project
and the lifecycle executor respects the versions given for a particular
project, no more MNG-1323.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
