Uploaded image for project: 'Maven JAR Plugin'
  1. Maven JAR Plugin
  2. MJAR-38

Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0
    • 2.1
    • None
    • None
    • Maven version: 2.0.4
      Microsoft Windows XP [Version 5.1.2600]

    Description

      I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package – an "extension" (or an extension of any other kind).
      I don't know why Maven is doing that.
      If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
      The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!

      Attachments

        1. MJAR-38.patch
          11 kB
          Mike Perham
        2. MJAR-38.patch
          11 kB
          Jochen Walz
        3. Jar Extension-Name Tester.zip
          3 kB

        Issue Links

          Activity

            People

              brett Brett Porter
              steevcoco Steven Coco
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: