[
https://issues.apache.org/jira/browse/MNG-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MNG-8028.
--------------------------------
Resolution: Incomplete
This issue is plain wrong. The inter module deps define topo sorting, and when
there is no link (or is lost due module being removed) the modules become
"independent" of each other. There is no "resolving" happening per se.
> 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)
