[
http://jira.jboss.com/jira/browse/DNA-174?page=comments#action_12420609 ]
Randall Hauch commented on DNA-174:
-----------------------------------
The desire to have single versions of 3rd party dependencies is only required for the
short-term. What we really want is to round out the Maven class loader functionality
(really, the utilities and tools around populating and managing a local Maven
"repository") so that sequencers, connectors, and other components can have any
dependencies they require. I would rather see effort put into that rather than effort
into automating this.
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