[
http://jira.codehaus.org/browse/MNG-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Magnay updated MNG-2426:
------------------------------
Attachment: bug.zip
Here is a demonstration project of the bug. It uses SWF and JBoss-SAR, though
it seems any combination of external plugins (e.g. cargo uberwar) will have the
same problem.
Just do an mvn install from the top level, and observe that what gets deployed
to your repo has the extension .jboss-sar, rather than the more correct .sar.
> Artifact copied to local repository with wrong file extension when using
> jboss-packaging plugin
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-2426
> URL: http://jira.codehaus.org/browse/MNG-2426
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Environment: jdk 1.5.0_06, maven 2.0.4, jboss-package-maven-plugin
> 2.0-SNAPSHOT (from mojo-sandbox SVN r2088)
> Reporter: Fredrik Vraalsen
> Fix For: 2.0.x
>
> Attachments: bug.zip
>
>
> 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>
> ...
--
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
