[
http://jira.codehaus.org/browse/MWAR-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203690#action_203690
]
Johan Sjöberg edited comment on MWAR-211 at 12/21/09 11:35 AM:
---------------------------------------------------------------
If "File Name Mapping" renames TLDs etc. as well, perhaps a tag like
<archiveName>myname.jar</archiveName> would be great to complement
<archiveClasses>true</archiveClasses>; to be able to replace the default
<artefactId>-<version>.jar with myname.jar.
was (Author: draenor):
Simply put, when using "<archiveClasses>true</archiveClasses>" to archive
classes into a jar-file it would be necessary to be able to name the produced
file to something other than<artefactId>-<version>.jar, as identified by Paulo.
The new tag could be something similar to "<archiveName>a name</archiveName>".
> Ability to rename a dependency's jar when putting it on the lib folder
> ----------------------------------------------------------------------
>
> Key: MWAR-211
> URL: http://jira.codehaus.org/browse/MWAR-211
> Project: Maven 2.x WAR Plugin
> Issue Type: New Feature
> Reporter: Magno Machado Paulo
> Attachments: TestMaven.rar
>
>
> Maven put on my 'lib' folder the jars of my project's dependencies named like
> <artefactId>-<version>.jar
> This is a problem when we need to reference the jar filename from sourcecode,
> because if we change the dependency version, we have to track all source code
> references to it and correct them. This is the case when importing a taglib
> into a jsp page
> It would be better if Maven put only <artefactId>.jar on the lib folder. And
> even better if it let us use any custom name we want for the dependencies. If
> no name is specified, then it could use the current pattern.
--
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
