You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2022/11/08 10:36:00 UTC

[jira] [Updated] (MRESOLVER-283) Introduce resolver wide "fork join pool" service

     [ https://issues.apache.org/jira/browse/MRESOLVER-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MRESOLVER-283:
--------------------------------------
    Summary: Introduce resolver wide "fork join pool" service  (was: Introduce resolver wide "shared" executor service)

> Introduce resolver wide "fork join pool" service
> ------------------------------------------------
>
>                 Key: MRESOLVER-283
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-283
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>
> More and more component in resolver does parallel processing (BF collector, MD resolver, basic connector), and they all create, maintain their own executor instance.
> Instead of this, create one shared service component and just reuse it accross resolver.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)