maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé (JIRA) <>
Subject [jira] [Commented] (MDEP-516) Go-offline does not find module dependencies in multi-module build.
Date Tue, 06 Jun 2017 03:06:18 GMT


Hervé commented on MDEP-516:

Any update on this? MDEP-516 and MDEP-204 are still open without any roadmap.
I do not see the purpose of going offline if I have to run package phase before being able
to do so.
I was expecting excludeGroupIds to help me but it has no effect so there is no solution, which
is annoying...

> Go-offline does not find module dependencies in multi-module build.
> -------------------------------------------------------------------
>                 Key: MDEP-516
>                 URL:
>             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:
> and I thought it must be a very normal scenario so probably a lot of other people are
> 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

View raw message