[
https://jira.codehaus.org/browse/MSHARED-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHARED-146.
----------------------------------
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.
> Using {artifact-id} as Extension-Name creates MANIFEST that does not function
> with Optional Package mechanism
> -------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-146
> URL: https://jira.codehaus.org/browse/MSHARED-146
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4
> Reporter: Ryan Sutter
>
> When generating MANIFEST files with Extensions listed within, Maven uses
> {artifact-id} as the extension name rather than acquiring the correct
> extension name from the extension artifact. As a consequence, the resulting
> MANIFEST file references a non-existent artifact when deployed in a J2EE
> container.
> A specific example is Apache commons-logging. The artifact-id is
> "commons-logging" but the extension name given within the artifact is
> org.apache.commons.logging. Maven generates a file that refers to
> "commons-logging" as the extension when it should be referring to
> org.apache.commons.logging resulting in a missing dependency at run-time.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
