Uploaded image for project: 'Maven Assembly Plugin'
  1. Maven Assembly Plugin
  2. MASSEMBLY-247

versions of included dependencies in multi-module projects are not deterministic

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • 2.2-beta-2
    • None
    • None
    • None
    • Maven 2.0.4 an assembly plugin 2.2-SNAPSHOT

    Description

      There is a problem with including dependency jars in an assembly. The resoultion of the version of the dependencies is not deterministic. The attached zipfile contains three projects, assembly, module-One and modue-Two. the assembly project is the aggregator of module-One and module-Two. module-One has a dep to junit 3.8.1, module-Two to junit 4.0. The assembly project contains a DependencyManagement with a dependency to junit 4.0. After executing 'mvn clean package ' in the assembly project the resulting zip file assembly-1.0-SNAPSHOT-luna.zip contains junit 3.8.1, after 'mvn clean install' it contains junit 4.0.
      Sometimes its the other way around, but playing with both commands shows that the resulting version of junit is not deterministic.

      Attachments

        Issue Links

        Activity

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

          People

            jdcasey John Dennis Casey
            sibay Tarek El-Sibay
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment