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

Go-offline does not find module dependencies in multi-module build.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.10
    • Fix Version/s: None
    • Component/s: go-offline
    • Labels:
      None

      Description

      Hello,

      I've recently hit the exact same problem that these guys are having:

      http://stackoverflow.com/questions/14694139/how-to-resolve-dependencies-between-modules-within-multi-module-project

      and I thought it must be a very normal scenario so probably a lot of other people are hitting.

      So basically I have a multi-module build where moduleA is built first and them moduleB depends on moduleA. However when I do mvn dependency:go-offline it comes to resolve the dependencies of moduleB and it fails with Artifact not found: moduleA.

      That seems to happen because only modules that have been packaged are put in the reactor and so later modules will know about them. So to fix it I have to do the following:

      mvn package dependency:go-offline -U -Pquick,test -DskipTests -s src/main/resources/settings.xml
      

      which I really don't like, because it does an extra package that I don't need, and then the whole build gets a lot slower.

      of course, mvn install at any time fixes the issue also, but I don't want to install

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rfscholte Robert Scholte
                Reporter:
                paranoiabla Petar Tahchiev
              • Votes:
                13 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: