You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Markku Saarela (JIRA)" <ji...@codehaus.org> on 2010/04/17 13:28:12 UTC

[jira] Created: (MSHARED-147) Maven Archiver does not obey project.build.finalName in Class-Path entry

Maven Archiver does not obey project.build.finalName in Class-Path entry
------------------------------------------------------------------------

                 Key: MSHARED-147
                 URL: http://jira.codehaus.org/browse/MSHARED-147
             Project: Maven Shared Components
          Issue Type: Bug
          Components: maven-archiver
    Affects Versions: maven-archiver-2.4
         Environment: Maven 2.2.1 and 3.0-alpha-7
            Reporter: Markku Saarela
         Attachments: MJAR-61.zip

Defining final names in dependency projects pom.xml does not affect generated manifest file classpath:
Class-Path: module-jar-1-1.0-SNAPSHOT.jar common-jar-1.0-SNAPSHOT.jar

There is issue in maven-jar-plugin witch actual cause is this issue MJAR-61. Also maven-war-plugin has same behavior.

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