[
http://jira.codehaus.org/browse/MASSEMBLY-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-203:
---------------------------------
Fix Version/s: 2.3-beta-1
> assembly:attached creates empty assemblies in reactor builds, but works fine
> in normal builds
> ---------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-203
> URL: http://jira.codehaus.org/browse/MASSEMBLY-203
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: java version "1.5.0_09"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
> Reporter: Graham Leggett
> Fix For: 2.3-beta-1
>
>
> When attaching an assemply to the package phase as below, and running mvn
> install, the assembly is built without a problem.
> If however the assembly is a sub-artifact built as part of a reactor /
> multimodule build, mvn install in the root pom produces an empty assembly.
> The kludge workaround is to cd to the assembly artifact directory and run mvn
> install from there.
> <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>
--
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
