[
http://jira.codehaus.org/browse/MWAR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MWAR-98.
----------------------------
Assignee: Olivier Lamy
Resolution: Duplicate
> Renaming artifact to its finalName in POM before placed in /WEB-INF/lib.
> ------------------------------------------------------------------------
>
> Key: MWAR-98
> URL: http://jira.codehaus.org/browse/MWAR-98
> Project: Maven 2.x War Plugin
> Issue Type: Improvement
> Affects Versions: 2.0.2
> Reporter: Thomas Raehalme
> Assignee: Olivier Lamy
>
> If you have project A with module core, it produces an artifact named
> core-x.y.z.jar (or any other type). Even if build/finalName has been
> specified in the POM, the file name still matches the name of the artifact
> when stored in the Maven repository. This is also the name that the WAR
> plug-in uses when adding the artifact to /WEB-INF/lib. If you add a module
> named core in project B, there will be two core-x.y.z.jar files when creating
> a WAR/EAR.
> There has been discussion about storing the artifact in the repository using
> the finalName value, but such implementation would make automatic downloading
> of artifacts much more difficult. It was therefore suggested that each plugin
> should rename the artifact itself when necessary.
> http://www.nabble.com/Re%3A-Question-regarding-finalName-in-maven-assembly-plugin-p9960876s177.html
> Therefore I suggest that the WAR plug-in renames the artifact to its
> finalName before adding it to the web application. Unfortunately I cannot
> provide a patch at the time of writing this. I will, however, try to provide
> one in the near future.
--
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
