maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MDEP-516) Go-offline does not find module dependencies in multi-module build.
Date Wed, 14 Sep 2016 21:36:20 GMT


Robert Scholte commented on MDEP-516:

The {{requiresDependencyCollection =true}} is the first step. This will ensure that that the
pom files for all dependencies are available. Next step would be to download the actual dependencies,
excluding the reactor projects.
The goal should also execute {{resolve-plugins}}, but based on your exception there's a bug
there too. Maybe only the plugins are downloaded, but not their dependencies?

> 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