Maven Shared Components

Using {artifact-id} as Extension-Name creates MANIFEST that does not function with Optional Package mechanism

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: maven-archiver-2.4
  • Fix Version/s: None
  • Component/s: maven-archiver
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

There are no comments yet on this issue.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated: