[maven-bug] Closed: (MAVEN-267) Increase the performance of the dependency resolver

[bo...@werken.com]

Message:

   The following issue has been closed.

   Resolver: Ben Walding
       Date: Thu, 13 Feb 2003 5:38 AM

o Created DependencyResolverInterface (DRI) from existing DependencyResolver
o Moved existing DependencyResolver to GraphDependencyResolver (implements DRI)
o Created WerkzDependencyResolver (implements DRI)
o Created new DependencyResolver that proxied calls to the chosen implementation
o Can choose impl at runtime via system property maven.core.dependencyresolver (class name of dep resolver, must implement DRI). I'd expect this will be removed before b9 hits the shelves. Makes test cases easy to write though!

o Resolution went from minutes to < 100ms.  Overall reactor init went from minutes to around 30 seconds (1 second per pom loaded).
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-267


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-267
    Summary: Increase the performance of the dependency resolver
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
   Estimate: 2 hours

    Project: maven
  Component: None

   Assignee: Ben Walding
   Reporter: Ben Walding

    Created: Thu, 13 Feb 2003 5:35 AM
    Updated: Thu, 13 Feb 2003 5:38 AM

Description:
The existing dependency resolver uses a persistent graph from commons-graph to resolve deps.  It uses Floyd's algorithm with has performance O(n^3).

Replace the dep resolver with werkz based resolver.  Optionally keeping old method as fallback.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira