[jira] Moved: (MSHARED-32) Customization of jar-name pattern of classpath-entries inside MANIFEST.MF

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSHARED-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-3573 to MSHARED-32:
------------------------------------------

    Affects Version/s:     (was: 2.0.8)
          Component/s:     (was: maven-archiver)
                       maven-archiver
                  Key: MSHARED-32  (was: MNG-3573)
              Project: Maven Shared Components  (was: Maven 2)

> Customization of jar-name pattern of classpath-entries inside MANIFEST.MF
> -------------------------------------------------------------------------
>
>                 Key: MSHARED-32
>                 URL: http://jira.codehaus.org/browse/MSHARED-32
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-archiver
>            Reporter: manuel aldana
>            Priority: Critical
>
> i followed manifest-customation as explained in:
> http://maven.apache.org/shared/maven-archiver/index.html
> what i really miss, is to configure the classpath pattern of the dependency jar-names. the only customization of classpath entries is possible by setting the classpath prefix (<addClasspath>) and (<classpathMavenRepositoryLayout/>). unfortunately it is not possible to set the jar-name pattern itself.
> to avoid library name-clashes we got pattern $groupId-$artifactId-$version for jars which are put besides the main-jar. by default maven-archiver only sets $artifactId-$version. so it would be nice to have a possible configuration like <jarPattern> or similar inside maven archive-configuration .

-- 
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