[MENFORCER-185] Require Release Dependencies ignorant about aggregator build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.3.1
• Fix Version/s: 3.0.0
• Component/s: Standard Rules
• Assignee: Unassigned
• Reporter: Thomas Diesler
• Created: 26/Feb/14 02:39
• Updated: 24/Jul/21 12:31
• Resolved: 30/Dec/20 00:52

Description

If A depends on B it is ok for A-1.0.0-SNAPSHOT to have snapshot dependency on B-1.0.0-SNAPSHOT if B was build before A during the same reactor build.

Using the requireReleaseDeps rule it seems that SNAPSHOTS are generally not allowed even when they belong to the same project and were built during the same reactor build.

We have a complex project with 100+ modules. I want to enforce that no module has dependencies on project SNAPSHOTS that were not included in the build. In such case A would use a stale version of B that happened to be available in the local/remote maven repository.

Issue Links

• depends upon: MENFORCER-186 Create a rule for the reactor (ReactorModuleConvergence)
• links to: GitHub Pull Request #34