[MNG-8028] Maven3 "resolves" in-reactor dependency if there is main artifact present

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 4.0.x-candidate
• Component/s: Core
• Assignee: Unassigned
• Reporter: Tamas Cservenak
• Created: 26/Jan/24 11:33
• Updated: 15/Apr/24 09:37

Description

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

Issue Links

• relates to: MNG-8096 Inconsistent dependency resolution behaviour for concurrent multi-module build can cause failures