maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Bray (JIRA)" <>
Subject [jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo
Date Tue, 08 Mar 2011 12:00:22 GMT


Jason Bray commented on MDEP-273:

I agree.  Brian, I know there has been discussion in the past about creating a pluggable architecture
around the algorithm used for transitive dependency resolution.  While I think that's a great
idea, in the immediate term this gets us much of the value at a significantly lower cost as
the highest version algorithm is the major alternative to the current algorithm.  Additionally,
reporting on managed dependency mismatches using the highest version algorithm adds a lot
of value.

I know our operations would begin running this report prior to any release that included dependency/version
changes.  Can you (or anyone else) comment on the chances of inclusion?

> 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