[ 
http://jira.codehaus.org/browse/MNG-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter closed MNG-636.
----------------------------

    Resolution: Won't Fix

I believe the dependency plugin does this now

> need a dependency usage analysis plugin
> ---------------------------------------
>
>                 Key: MNG-636
>                 URL: http://jira.codehaus.org/browse/MNG-636
>             Project: Maven 2
>          Issue Type: New Feature
>            Reporter: Brett Porter
>            Priority: Minor
>
> 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

        

Reply via email to