Using {artifact-id} as Extension-Name creates MANIFEST that does not function
with Optional Package mechanism
-------------------------------------------------------------------------------------------------------------
Key: MSHARED-146
URL: http://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 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
