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

[Johnny Verhaeg (JIRA)]

    [ http://jira.jboss.com/jira/browse/DNA-174?page=comments#action_12420819 ] 
            
Johnny Verhaeg commented on DNA-174:
------------------------------------

Regarding Randall's comment, I specified in this issue's title that the concern is only within a single class loader.  So although I agree we should be spending effort on the Maven class loader functionality, this will remain a concern beyond that.

> 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