maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MDEP-516) Go-offline does not find module dependencies in multi-module build.
Date Sat, 16 Jan 2016 13:53:39 GMT

    [ https://issues.apache.org/jira/browse/MDEP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103196#comment-15103196
] 

Hervé Boutemy commented on MDEP-516:
------------------------------------

thinking at it: isn't it the difference between dependency collection and resolution (available
only in Maven 3)?
then isn't it about the mojo using dependency resolution (ie downloading artifacts automatically)
when it should use dependency collection (ie without downloading artifact) then decide which
artifacts to download or not?
of course, this would require to be Maven 3 specific

> 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)

Mime
View raw message