[dna-issues] [JBoss JIRA] Commented: (DNA-174) Should ensure single versions required for 3rd-party dependencies within same classloader

[Paul Gier (JIRA)]

    [ http://jira.jboss.com/jira/browse/DNA-174?page=comments#action_12420618 ] 
            
Paul Gier commented on DNA-174:
-------------------------------

You probably want to look at the maven dependency plugin [1] if you haven't already.  

{noformat} mvn dependency:tree -Dverbose=true {noformat} 

This will create a text based tree listing of all the project dependencies.  Maven collapses project dependencies to a single version using a _nearest_ mechanism for dependency resolution.  This means that dependency versions specified in the pom will take priority over the same transitive dependency.  And a transitive dependency one level away from the pom will take priority over a version specified two levels deep.

There is also a report that can be used to create an html report of the dependencies:
{noformat}mvn project-info-reports:dependencies{noformat}

This will create a report in the directory "target/site/dependencies.html"

[1]http://maven.apache.org/plugins/maven-dependency-plugin/index.html

> Should ensure single versions required for 3rd-party dependencies within same classloader
> -----------------------------------------------------------------------------------------
>
>                 Key: DNA-174
>                 URL: http://jira.jboss.com/jira/browse/DNA-174
>             Project: DNA
>          Issue Type: Task
>          Components: Development Environment
>    Affects Versions: 0.1
>            Reporter: Johnny Verhaeg
>            Priority: Minor
>             Fix For: 0.2
>
>
> We should write a script that will be executed after the build and produce some reports indicating:
> - The list of 3rd-party dependencies, both direct & indirect
> - Any potential conflicts in dependency versions between projects or other dependencies
> - A tree of non-test-related dependencies by project
> Developers would then need only to add classloader knowledge into the mix when handling dependency version conflict resolution.  It would be nice if the resulting reports could be accessed in the same manner as build & test results via Hudson.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira