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

["Karl Heinz Marbaise (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MENFORCER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342917#comment-342917 ] 

Karl Heinz Marbaise commented on MENFORCER-185:
-----------------------------------------------

See MENFORCER-186 which is exactly what you need. I'm currently working on such rule.

> Require Release Dependencies ignorant about aggregator build
> ------------------------------------------------------------
>
>                 Key: MENFORCER-185
>                 URL: https://jira.codehaus.org/browse/MENFORCER-185
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 1.3.1
>            Reporter: Thomas Diesler
>
> 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
(v6.1.6#6162)