[
http://jira.codehaus.org/browse/MENFORCER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MENFORCER-19.
------------------------------------
Resolution: Won't Fix
With some flags set,
[maven-dependency-plugin|http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html]
can be used to enforce dependencyManagement. A little verbose, but does the
job well.
{code:xml}
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>analyze-dep-mgt</goal>
</goals>
<phase>verify</phase>
<configuration>
<failBuild>true</failBuild>
<ignoreDirect>false</ignoreDirect>
</configuration>
</execution>
</executions>
</plugin>
{code}
> 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
