You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ruel loehr (JIRA)" <ji...@codehaus.org> on 2006/03/10 18:13:23 UTC
[jira] Commented: (MNG-2128) Add an option to enforce
dependencyManagement
[ http://jira.codehaus.org/browse/MNG-2128?page=comments#action_60680 ]
ruel loehr commented on MNG-2128:
---------------------------------
This is hot. For an enterprise level app, this option would be tremendously welcome, specifically regarding transitive dependencies. We want to lock down the versions used at the top level, and enforce it among subprojects.
> Add an option to enforce dependencyManagement
> ---------------------------------------------
>
> Key: MNG-2128
> URL: http://jira.codehaus.org/browse/MNG-2128
> Project: Maven 2
> Type: New Feature
> Components: Dependencies
> Versions: 2.0.3, 2.0, 2.0.1, 2.0.2
> 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