Maven Shared Components

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

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
  • Environment:
    Maven 2.2.1 and 3.0-alpha-7
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

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.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MJAR-61 Manifest classpath ignores the "real" JAR filenames specified in <finalName>

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Markku Saarela
Vote (3)
Watch (1)

Dates

  • Created:
    Updated: