[
http://jira.codehaus.org/browse/MENFORCER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257282#action_257282
]
Joe Littlejohn commented on MENFORCER-19:
-----------------------------------------
Nicolas, I notice that with the previous comment you marked this as WontFix. It
seems like it would be nice to add a new enforcer rule based on the
maven-dependency-plugin:analyze-dep-mgt (as suggested by Brian and jieryn
above).
This would be a useful rule which could be available and documented without
having to use the above workaround.
> Add an option to enforce dependencyManagement
> ---------------------------------------------
>
> Key: MENFORCER-19
> URL: http://jira.codehaus.org/browse/MENFORCER-19
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Reporter: Carlos Sanchez
>
> 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
