maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <>
Subject [jira] [Updated] (MENFORCER-185) Require Release Dependencies ignorant about aggregator build
Date Tue, 15 Nov 2016 02:32:58 GMT


Guillaume Boué updated MENFORCER-185:
    Attachment: MENFORCER-185.patch

I have attached a working patch for this, see {{MENFORCER\-185.patch}}. It passes all 9 ITs
I added with Maven 3.0.5 and 3.3.9 (on Ubuntu & Windows). However, it requires a signature
change of an abstract method (namely {{AbstractBanDependencies#checkDependencies}}), so it
would break current implementations. I don't see a good way around that, so I think this will
have to wait for a major upgrade.

> Require Release Dependencies ignorant about aggregator build
> ------------------------------------------------------------
>                 Key: MENFORCER-185
>                 URL:
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 1.3.1
>            Reporter: Thomas Diesler
>             Fix For: more-investigation
>         Attachments: MENFORCER-185.patch,
> 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

View raw message