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

Version range dependencies not resolved from the reactor

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      When using modules that have independent version numbers (that is, modules in the same project may have different version numbers), it's commonplace to specify dependencies between modules with version ranges when using semantic versioning.

      For some reason, when version ranges are used on dependencies that refer to modules that are part of the project (and therefore should be in the reactor), the assembly plugin ignores them and tries to resolve them from the local repository instead.

      The following project reproduces this issue (just "mvn clean package"):

      https://github.com/io7m/independent-versioning-20170207

      Interestingly, this didn't happen with the same assembly plugin on older Maven versions. Here's a successful build on Travis CI:

      https://travis-ci.org/io7m/independent-versioning-20170207

        Attachments

        1. mvn.log.gz
          25 kB
          Mark Raynsford

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                io7m Mark Raynsford
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: