[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_67154 ]
David Boden commented on MASSEMBLY-97:
--------------------------------------
I have worked around this by using "single" as the goal rather than "assembly".
The "single" goal has been added as a workaround for this issue until the
maven core can provide better multi-project support.
This works for me:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
<configuration>
<archive>
<manifestFile>META-INF/MANIFEST.MF</manifestFile>
</archive>
<descriptors>
<descriptor>../SSBuild/bundle-assembly.xml</descriptor>
</descriptors>
</configuration>
</plugin>
> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
> Key: MASSEMBLY-97
> URL: http://jira.codehaus.org/browse/MASSEMBLY-97
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Nigel Magnay
> Priority: Critical
> Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> The attached project has a (very simple) multiproject build.
> If you edit the root pom.xml and comment out project2, then "mvn install"
> will execute correctly and build and assemble the jar files, and deploy them
> to the local repo.
> If you have both project1 and project2, then something odd happens - it fails
> building the package for item1, but the error report is that there is a
> missing dependency for item2's package - which it hasn't built yet.
> This means that 'root level' builds for us can't be executed from a clean
> system as they always fall over.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
