You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Cole Mickens (JIRA)" <ji...@codehaus.org> on 2010/07/07 16:51:33 UTC

[jira] Created: (MDEP-273) Analyze Dependency Versions Mojo

Analyze Dependency Versions Mojo
--------------------------------

                 Key: MDEP-273
                 URL: http://jira.codehaus.org/browse/MDEP-273
             Project: Maven 2.x Dependency Plugin
          Issue Type: Improvement
    Affects Versions: 2.2
            Reporter: Cole Mickens
            Assignee: Brian Fox
         Attachments: analyze-dep-versions.patch

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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Martijn Verburg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259296#action_259296 ] 

Martijn Verburg commented on MDEP-273:
--------------------------------------

This would be a very useful patch for us!  The more analysis options we get, the better.

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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, 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243234#action_243234 ] 

Cole Mickens commented on MDEP-273:
-----------------------------------

Sorry Brian, I'm not entirely sure what you're looking for Brian. Can you elaborate?

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Issue Comment Edited: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243234#action_243234 ] 

Cole Mickens edited comment on MDEP-273 at 11/15/10 11:23 PM:
--------------------------------------------------------------

Sorry Brian, I'm not entirely sure what you're looking for. Can you elaborate?

      was (Author: cole.mickens):
    Sorry Brian, I'm not entirely sure what you're looking for Brian. Can you elaborate?
  
> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Jason Bray (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259313#action_259313 ] 

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: http://jira.codehaus.org/browse/MDEP-273
>             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, 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cole Mickens updated MDEP-273:
------------------------------

    Attachment: analyze-dep-versions-1.patch

Same as before, svn update, svn add --force *, svn diff > anaylze-dep-versions-1.patch.

Hopefully this is acceptable or at the very least closer to being acceptable.

(This patch includes the original patch as well, in addition to the documentation updates)

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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, 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Sean Griffin (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264213#action_264213 ] 

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 everyone.

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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, 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cole Mickens updated MDEP-273:
------------------------------

    Attachment: script-ant.PNG
                core.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: http://jira.codehaus.org/browse/MDEP-273
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Issue Comment Edited: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251089#action_251089 ] 

Cole Mickens edited comment on MDEP-273 at 1/10/11 4:00 PM:
------------------------------------------------------------

Same as before, svn update, svn add --force *, svn diff > anaylze-dep-versions-1.patch.

Hopefully this is more acceptable!

(This patch includes the original patch as well, in addition to the documentation updates)

      was (Author: cole.mickens):
    Same as before, svn update, svn add --force *, svn diff > anaylze-dep-versions-1.patch.

Hopefully this is acceptable or at the very least closer to being acceptable.

(This patch includes the original patch as well, in addition to the documentation updates)
  
> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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, 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Cole Mickens (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cole Mickens updated MDEP-273:
------------------------------

    Attachment: analyze-dep-versions.patch

This is the patch that includes the Mojo, Report and parser (for the report) as well as the 6 additional IT tests.

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Cole Mickens
>            Assignee: Brian Fox
>         Attachments: analyze-dep-versions.patch
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242250#action_242250 ] 

Brian Fox commented on MDEP-273:
--------------------------------

can you provide a patch to add proper site updates for your new goal?

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243252#action_243252 ] 

Brian Fox commented on MDEP-273:
--------------------------------

We usually add a small section to the usage page describing the new goal and how it's used.

> Analyze Dependency Versions Mojo
> --------------------------------
>
>                 Key: MDEP-273
>                 URL: http://jira.codehaus.org/browse/MDEP-273
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira