[MASSEMBLY-179] Assembled jar includes artifact names in path

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.2-beta-2
• Assignee: John Dennis Casey
• Reporter: Jonathan Komorek
• Created: 22/Jan/07 10:17
• Updated: 01/Feb/08 10:37
• Resolved: 25/Jun/07 09:49

Description

This issue does not occur in 2.1 and began occurring in 2.2-SNAPSHOT (roughly) a couple months ago.
After assembling a jar, the path for each of the included files begins with what seems to be ${artifactId}-${version}.${packaging}
This includes files from dependent jars and files from sub-modules - all files.
The plugin is configured in the POM as follows:
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>1</id>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
</execution>
</executions>
<version>2.2-SNAPSHOT</version>
<configuration>
<descriptor>assembly.xml</descriptor>
</configuration>
</plugin>
</plugins>
</build>
The entire assembly.xml is as follows:
<assembly>
<id>dependencies</id>
<formats>
<format>jar</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<dependencySets>
<dependencySet>
<outputDirectory>/</outputDirectory>
<unpack>true</unpack>
<scope>runtime</scope>
</dependencySet>
</dependencySets>
</assembly>

Issue Links

• supercedes: MASSEMBLY-162 In a multiproject environment, assembly takes wrong dependencies