[
https://jira.codehaus.org/browse/MSHARED-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHARED-147.
----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Maven Archiver does not obey project.build.finalName in Class-Path entry
> ------------------------------------------------------------------------
>
> Key: MSHARED-147
> URL: https://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 was sent by Atlassian JIRA
(v6.1.6#6162)
