You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/07/27 05:56:58 UTC

[jira] Updated: (MNG-636) need a dependency usage analysis plugin

     [ http://jira.codehaus.org/browse/MNG-636?page=all ]

Brett Porter updated MNG-636:
-----------------------------

        Version:     (was: 2.0-beta-2)
    Fix Version: 2.0-beta-2

> need a dependency usage analysis plugin
> ---------------------------------------
>
>          Key: MNG-636
>          URL: http://jira.codehaus.org/browse/MNG-636
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-plugins
>     Reporter: Brett Porter
>      Fix For: 2.0-beta-2

>
>
> its quite easy for the dependency list of a project to get out of date - in particular, a project is no longer used but its dependency is still there, or you are compiling using a dependency that is only provided transitively, or a scope is too broad (used for testing but available for compiling).
> IT would be good to analyse the classes used in the source code, and which compile time dependencies provide them, and which are orphaned, and to break this down by those directly specified and those transtively specified.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org