M2 assembly problems with multi-module builds

[Jake Pezaro <Ja...@vcint.com>]

i am trying to bind assembly:assembly to the package phase in one of my
parent poms parent-1, the other parent is parent-2 which does not have
an assembly bound.  the assembly plugin is the 2.0.x svn version.

this works as expected when i check out a single project and install it.
ie the assembly is built and installed correctly.

when i check out my multi-module project, the children of parent-2 build
& install correctly, however the children of parent-1 do not get
installed and no assemblies are built at all.

it seems that the multi-module build executes correctly until it hits
the first parent-1 build.  when it hits this build, the build sequence
starts again and nothing gets installed.  for example, if i have a
multi-module build with 3 projects as below, that build in order p1, p2,
p3:

p1 - (non-assembly)
p2 - (assembly bound in parent)
p3 - (non-assembly)

execution is as follows for mvn install:

build p1
install p1
build p2
build p1
build p2
build p3

does anyone know why this might be happening?  does anyone know how the
assembly plugin alters the build lifecycle?

cheers

jake


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________