[
http://jira.codehaus.org/browse/MASSEMBLY-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-179:
---------------------------------
Priority: Blocker (was: Critical)
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>
was:
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>
> Assembled jar includes artifact names in path
> ---------------------------------------------
>
> Key: MASSEMBLY-179
> URL: http://jira.codehaus.org/browse/MASSEMBLY-179
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Jonathan Komorek
> Priority: Blocker
> Fix For: 2.2-beta-2
>
>
> 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>
--
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
