Are you sure Assembly is finding the assembly.xml you've specified
during the reactor build? I know paths specified in child pom plugins
sometimes don't work as expected during reactor builds, etc.
As a test, rename the assembly.xml file to .blah and run from child.
If the assembly plugin "looks" the same as when executed from the
parent directory, I'd assume this is what's going on.
Wayne
On 4/23/07, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all,
I have an assembly linked into the mvn build lifecycle like below using
the "attached" goal.
When mvn install is run from the assembly artifact, the assembly is built
correctly.
If however mvn install is run from the root pom (ie a reactor build), the
assembly plugin goes through the motions, but the assembly created is
empty.
Does the "attached" goal work in multi-module / reactor builds?
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1</version>
<configuration>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
</execution>
</executions>
</plugin>
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
