Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.2
-
Fix Version/s: 2.2-beta-2
-
Labels:None
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
-
Activity
I think it is an issue because:
1. the behavior is different than in 2.1 assembly plugin
2. as far as I know it is not documented
I had this problem when I switched from 2.1 to 2.2-SNAPSHOT.
I assume that when 2.2 will be released, people will have problems.
So it should be either corrected so that it works as in 2.1,
or it should be documented (with red color 
)...
)...
I think I've encountered the same issue. I use, in 2.1, to have a jar containing a merge of jars from submodules. No, inside the final jar, there is a root dir for project.
e.g.:
parent
sub-x
sub-y
will create a jar containing:
sub-x-0.1/.../my classes from sub-x
sub-y-0.1/.../my classes from sub-y
For <sources/>, the solution was to add <includeModuleDirectory>false</includeModuleDirectory> but it isn't supported for <binaries>. If definetly should and it it quite critical... I can't build my application anymore with this plugin.