maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Griffin (JIRA)" <>
Subject [jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo
Date Wed, 20 Apr 2011 15:53:22 GMT


Sean Griffin commented on MDEP-273:

Because this capability is absolutely essential to prevent incompatibility bugs from getting
out the door, a problem that has bitten us numerous times already, we're going to fork the
maven-dependency-plugin, strip out what doesn't apply to this new goal/report, and rename
it so that we can start using it.  We _really_ did not want to have to do this, but we simply
cannot continue with this fragility and no help from Maven to flag the issues.

Hopefully this patch eventually gets integrated into the broader plugin for the benefit of

> Analyze Dependency Versions Mojo
> --------------------------------
>                 Key: MDEP-273
>                 URL:
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Cole Mickens
>            Assignee: Brian Fox
>         Attachments: analyze-dep-versions-1.patch, analyze-dep-versions.patch, core.PNG,
> This is a patch that adds a new mojo and a report class to maven-dependency-plugin trunk
(2.2). The goal `dependency:analyze-dep-versions` lists dependencies that are either resolved
at a lower version than needed by a dependency farther from the project root or are being
overridden by the dependencyManagement section. In some sense it is complimentary to `dependency:analyze-dep-mgt`.
> I checked out trunk today, added my new files, `svn add`ed them, then performed an `svn
diff`. The patches applied correctly with a rechecked out copy of trunk with `cd apache-maven-dependency-plugin;
patch -p0 < ../analyze-dep-versions.patch`. After patching, it built, installed and passed
IT tests (including the 6 new ones that I've added) properly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message