[
https://issues.apache.org/jira/browse/MNG-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873174#comment-17873174
]
Tamas Cservenak commented on MNG-8028:
--------------------------------------
The problem is more with filtered builds (ie. use of -pl or alike) when "full"
reactor contains projects A, B, C (and assume they depend like C -> B -> A) and
user leaves out project B (ie. using -pl A,C).
In this case B is "out of scope" (and assume reachable from local repository),
and Maven will pick it up from there, but "existing B" (installed to local
repo) depends on "just being built in reactor C").
> Maven3 "resolves" in-reactor dependency if there is main artifact present
> -------------------------------------------------------------------------
>
> Key: MNG-8028
> URL: https://issues.apache.org/jira/browse/MNG-8028
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Which, is IMHO wrong. As if main artifact file is absent, it will try to
> download the reactor module from remote repository.
> A reactor module is "done" when all the lifecycles was executed on it. Maven
> should not imply anything about presence or absence of main artifact, as the
> build may not even build one (think "go offline" use cases or new skip
> capabilities).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
