You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2020/12/30 00:53:01 UTC
[jira] [Closed] (MENFORCER-185) Require Release Dependencies
ignorant about aggregator build
[ https://issues.apache.org/jira/browse/MENFORCER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz closed MENFORCER-185.
------------------------------------------
Fix Version/s: (was: 3.0.0)
Resolution: Duplicate
> Require Release Dependencies ignorant about aggregator build
> ------------------------------------------------------------
>
> Key: MENFORCER-185
> URL: https://issues.apache.org/jira/browse/MENFORCER-185
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
> Affects Versions: 1.3.1
> Reporter: Thomas Diesler
> Priority: Major
> Fix For: 3.0.0-M4
>
> Attachments: MENFORCER-185.patch, seuss.zip
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)