[
https://issues.apache.org/jira/browse/MDEP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15482460#comment-15482460
]
Petar Tahchiev commented on MDEP-516:
-------------------------------------
Any updates on this? It's a 7-year old issue with a huge impact on docker and
CI systems, and it would be nice to have to fixed before maven 3.4.0 Can you
guys give me some pointers where to look at? I don't think it's the dependency
plugin's fault.
> Go-offline does not find module dependencies in multi-module build.
> -------------------------------------------------------------------
>
> Key: MDEP-516
> URL: https://issues.apache.org/jira/browse/MDEP-516
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 2.10
> Reporter: Petar Tahchiev
>
> 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:
> {code}
> mvn package dependency:go-offline -U -Pquick,test -DskipTests -s
> src/main/resources/settings.xml
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
