Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-147

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • maven-archiver-2.4
    • None
    • maven-archiver
    • None
    • Maven 2.2.1 and 3.0-alpha-7

    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.

      Attachments

        1. MJAR-61.zip
          7 kB

        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.
          • Closed

          Activity

            People

              Unassigned Unassigned
              ivalo Markku Saarela
              Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: