[
https://issues.apache.org/jira/browse/MENFORCER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MENFORCER-63.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Fail the build on reactor dependency divergence
> -----------------------------------------------
>
> Key: MENFORCER-63
> URL: https://issues.apache.org/jira/browse/MENFORCER-63
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
> Priority: Major
>
> The maven-project-info-reports-plugin provides a dependency convergence
> report that guarantees that siblings under a reactor use the same versions.
> Maven enforcer should be able to fail the build if the dependencies don't
> converge.
> This is different from MENFORCER-19, which is tracked by analyze-dep-mgt,
> because it will only track differences between a parent's
> dependencyManagement section and the child's dependency section, not between
> siblings.
> So if the parent neglects to declare a dependency X in dependencyManagement,
> but one child uses X 1.0 and another child uses X 2.0, the dependency
> convergence report will catch it, but analyze-dep-mgt will not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
