[
http://jira.codehaus.org/browse/MNG-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106734
]
Brian Fox commented on MNG-2128:
--------------------------------
It would be consistent with the other enforcer rules such as "noSnapshots" and
"bannedDependencies"
I already have this code in dependency:analyze-dep-mgt. So I could make this a
rule fairly quickly. If you agree is the way to go, lets move the issue to
enforcer. (means you can get it in 2.0 and not have to wait for 2.1)
> Add an option to enforce dependencyManagement
> ---------------------------------------------
>
> Key: MNG-2128
> URL: http://jira.codehaus.org/browse/MNG-2128
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3
> Reporter: Carlos Sanchez
> Fix For: 2.1
>
>
> Add something to the dependencyManagement section like
> <enforce>true</enforce>
> to make build fail if a subproject uses a different version
> Currently a subproject can specify the version of a dependency already
> defined in dependencyManagement, which is error prone
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
