You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oleg Gusakov (JIRA)" <ji...@codehaus.org> on 2009/05/04 21:14:44 UTC
[jira] Closed: (MERCURY-120) convert list resolution into single
node resolution
[ http://jira.codehaus.org/browse/MERCURY-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov closed MERCURY-120.
--------------------------------
Resolution: Fixed
Changed DependencyTreeBuilder: eliminated mutiple tree creation. resolveConflicts() now builds a single dependency tree when supplied a list of artifact metadada to resolve together.
This resulted in approx. 2x speed increase on large (~50 MDs) resolutions
> convert list resolution into single node resolution
> ---------------------------------------------------
>
> Key: MERCURY-120
> URL: http://jira.codehaus.org/browse/MERCURY-120
> Project: Mercury
> Issue Type: Sub-task
> Components: Dependency Builder
> Affects Versions: 1.0-alpha-8
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> Currently, a multi-artifact resolution creates a dependency tree for each supplied artifact, then creates a tree out of them all and resolves conflicts. This was done as a quick solution when API changed to accomodate multi-artifact use case: processing a POM, Maven resolve API
> Better solution would be to create a single tree with all those artifacts as dependencies and build only this tree (then resolve conflicts). This would allow to eliminate multiple creation of the shared sub-trees.
--
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