You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Anita Kulshreshtha (JIRA)" <ji...@apache.org> on 2007/05/30 18:51:16 UTC

[jira] Commented: (GERONIMO-3192) use mvn dependency:analyze to clean up dependencies

    [ https://issues.apache.org/jira/browse/GERONIMO-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500192 ] 

Anita Kulshreshtha commented on GERONIMO-3192:
----------------------------------------------

I tried mvn dependency:analyze on geronimo-axis2. The tool is helpful in finding _possibly_ unused dependencies. It treats 'test' scoped and 'generate-test-sources' phase dependencies as unused dependencies.  The 'dependency mismatch' information is very useful. Does anyone know why we have so many excludes in the main pom? According to dependency Resolved/DM information we are using older versions of the excluded dependencies!!  

> use mvn dependency:analyze to clean up dependencies
> ---------------------------------------------------
>
>                 Key: GERONIMO-3192
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3192
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: Wish List
>            Reporter: David Jencks
>
> Maven seems to have a tool to help analyze whether the dependencies in a pom are those actually used and needed.  I ran mvn dependency:analyze and it looks to me like we could make some improvements.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.