maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Brown (JIRA)" <>
Subject [jira] Commented: (MNG-3379) Parallel resolution of artifacts
Date Sun, 03 Feb 2008 22:53:58 GMT


Don Brown commented on MNG-3379:

I substituted it in my local repo.  In my latest -db release, I changed the version to be
more clear.

> Parallel resolution of artifacts
> --------------------------------
>                 Key: MNG-3379
>                 URL:
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.8
>            Reporter: Don Brown
>            Assignee: Brett Porter
>         Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, parallel-resolution.diff
> Artifacts should be resolved in parallel, grouped by group id's to get around the lack
of synchronization in the local repository.  The patch does the following:
> * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care not to
resolve multiple artifacts from the same group id simultaneously. (requires Java 5)
> * Makes the http wagon the default instead of the poor performing http-client
> Disadvantages: 
> * Requires Java 5, but the backport jars could be substituted pretty easily
> * Breaks some plugins due to commons-logging being in the Maven uber jar (required by
commons-httpclient), notably the apt plugin (maybe more should use the isolatedRealm setting?)
> * Screws up the progress monitor as multiple threads are updating it
> Advantages:
> * Much faster when combined with the http wagon (WAGON-98).  I was seeing 40% improvement
on some test builds.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message