Uploaded image for project: 'Maven Dependency Plugin'
  1. Maven Dependency Plugin
  2. MDEP-32

-Sibling Dependency Not Included in copy-dependencies output during multi-project build

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None
    • None

    Description

      Using the following structure

      dependency-test

      • module1
      • module2

      I have the dependency-maven-plugin:copy-dependencies goal attached
      the package phase of the module2 module.

      "module2" has a dependency on "module1". When I run "mvn package" from the
      "module2" folder, it correctly includes the "module1" jar in the
      target/dependency folder.

      When I run "mvn package" from the "dependency-test" folder, the "module1" jar is
      not included in the impl/target/dependency folder.

      A simple example of the problem is attached.

      Attachments

        1. dependency-revised.zip
          3 kB
          Matt Brozowski

        Issue Links

          Activity

            brozow Matt Brozowski added a comment -

            I have reopened this because it doesn't appear to be fixed in maven-dependency-plugin.

            I have revised the original test to use the maven-dependency-plugin and am attaching it.

            Matt Brozowski

            brozow Matt Brozowski added a comment - I have reopened this because it doesn't appear to be fixed in maven-dependency-plugin. I have revised the original test to use the maven-dependency-plugin and am attaching it. Matt Brozowski

            this issue duplicates MDEP-44

            brianf@infinity.nu Brian E. Fox (imported) added a comment - this issue duplicates MDEP-44

            People

              brianf Brian E Fox
              brozow Matt Brozowski
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: