Uploaded image for project: 'Maven WAR Plugin'
  1. Maven WAR Plugin
  2. MWAR-167

Final manifest not written to exploded location

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1-alpha-1
    • 2.6
    • manifest
    • None
    • Patch

    Description

      When I open up my generated WAR file, the Manifest file contains all the entries I specified. This is correct. However, when I look into the exploded location, it's just the file I had in my project to begin with.

      The exploded Manifest should be updated with the final contents.

      Attachments

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. MWAR-353 Manifest still not written to exploded location

        • Major - Major loss of function.
        • Open

        Bug - A problem which impairs or prevents the functions of the product. MWAR-340 <packagingExcludes> is ignored by war:exploded

        • Major - Major loss of function.
        • Closed
        supercedes

        New Feature - A new feature of the product, which has yet to be developed. MWAR-233 Please allow for MANIFEST.MF in exploded

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            khmarbaise Karl Heinz Marbaise
            pbenedict Paul Benedict
            Votes:
            12 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment