[MDEP-516] Go-offline does not find module dependencies in multi-module build.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.10
• Component/s: go-offline
• Assignee: Robert Scholte
• Reporter: Petar Tahchiev
• Created: 16/Jan/16 12:34
• Updated: 22/Nov/19 02:42
• Resolved: 21/Nov/19 18:07

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

Issue Links

• duplicates: MDEP-204 go-offline fails to resolve artifact available in maven reactor