maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cole Mickens (JIRA)" <>
Subject [jira] Updated: (MDEP-273) Analyze Dependency Versions Mojo
Date Wed, 07 Jul 2010 15:55:32 GMT


Cole Mickens updated MDEP-273:

    Attachment: script-ant.PNG

I'm attaching two example reports. These were generating from executing `mvn dependency:analyze-dep-versions
site` after altering the maven-2.2.1 tagged release pom.xml to use the snapshot of the m-d-p
with my additions.

There are a few projects in the maven reactor build that have mismatched dependencies. Depending
on the changes between the versions of these plugins, there could perhaps be bugs that would
not be obvious at first glance.

They're screenshots because the HTML would look bad without the CSS as well.

> 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.patch, core.PNG, script-ant.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