[
https://jira.codehaus.org/browse/MENFORCER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343873#comment-343873
]
jieryn commented on MENFORCER-185:
----------------------------------
Karl, MENFORCER-186 is not what we need for the original problem here. The
requireReleaseDeps rule will fail the build if modules in the same reactor
depend on one another and are at -SNAPSHOT release levels. This kind of thing
is typical in a multi-module build.
I think we do want MENFORCER-186 to validate -SNAPSHOT sanity within a reactor,
but we also want to be tolerant of -SNAPSHOT versions for dependencies when we
are in the same reactor; It is perfectly fine to fail the build if it has
-SNAPSHOT outside of the reactor. This requireReleaseDeps is practically
useless as it stands today.
> 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)
