[MNG-2426] Artifact copied to local repository with wrong file extension when using jboss-packaging plugin

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.4
• Component/s: Artifacts and Repositories
• Environment: jdk 1.5.0_06, maven 2.0.4, jboss-package-maven-plugin 2.0-SNAPSHOT (from mojo-sandbox SVN r2088)
• Assignee: John Dennis Casey
• Reporter: Fredrik Vraalsen
• Created: 07/Jul/06 11:21
• Updated: 30/Jul/09 16:18
• Resolved: 30/Jul/09 16:18

Description

When using the jboss-packaging plugin and setting <packaging> to jboss-sar in my pom, the artifact is copied into the local repository with the wrong file extension (.jboss-sar instead of .sar). The jboss-packaging components.xml has <extension> set to sar. The file in the build target directory has the correct .sar extension.

Here's the relevant excerpt from my pom.xml:

<packaging>jboss-sar</packaging>
...
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-packaging-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<extensions>true</extensions>
...

Issue Links

• duplicates: MNG-3506 Custom ArtifactHandler not resolved for project when an additional plugin with extensions is defined in parent pom
• duplicates: MNG-1682 Plugins do not honor the correct extension when run as a part of a multiproject build
• relates to: MNG-2240 Handling of custom lifecycle artifacts is not working properly