maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Sjöberg (JIRA) <>
Subject [jira] Commented: (MWAR-211) Ability to rename a dependency's jar when putting it on the lib folder
Date Mon, 21 Dec 2009 17:29:55 GMT


Johan Sjöberg commented on MWAR-211:

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:
>             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:
For more information on JIRA, see:


View raw message