[jira] (MWAR-211) Ability to rename a dependency's jar when putting it on the lib folder

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MWAR-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309727#comment-309727 ] 

Dennis Lundberg commented on MWAR-211:
--------------------------------------

The solution for the original problem in this issue is, as Benjamin mentioned, to add some configuration for the WAR Plugin, like this:

{code:xml}
        <configuration>
          <outputFileNameMapping>@{artifactId}@.@{extension}@</outputFileNameMapping>
        </configuration>
{code}
                
> Ability to rename a dependency's jar when putting it on the lib folder
> ----------------------------------------------------------------------
>
>                 Key: MWAR-211
>                 URL: https://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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira