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

CLONE - Created manifest contains versions of test scope

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

    Details

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

      Description

      I'd like to reopen the issue MSHARED-396.

      So the case is extremely simple:

      1. Maven module creates executable jar adding classpath to manifest.
      2. Then assembly plugin packs executable jar and it's dependencies into archive.
      3. Then we unpack app and launch it with java -jar myexecutable.jar. All dependencies are placed in same folder and referenced by manifest classpath.

      Now suppose we had one library of version 1.0 in runtime scope and 1.5 in test scope. Current behavior is that manifest classpath will have version 1.5 set, but assembly plugin will pack 1.0 cause we only take runtime dependencies. And this may result in ClassNotFoundException in production.

      Perhaps it has something to do with MSHARED-4?

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              dmitry.murashenkov Dmitry Murashenkov

              Dates

              • Created:
                Updated:

                Issue deployment