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 2024/01/11 12:32:00 UTC

[jira] [Assigned] (MNG-8007) Make Maven transfer listener used with Resolver more concurrent friendly

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

Tamas Cservenak reassigned MNG-8007:
------------------------------------

    Assignee: Tamas Cservenak

> Make Maven transfer listener used with Resolver more concurrent friendly
> ------------------------------------------------------------------------
>
>                 Key: MNG-8007
>                 URL: https://issues.apache.org/jira/browse/MNG-8007
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> Current console transfer listener used in Maven has all method {{synchronized}}. This becomes a problem as resolver is more and more parallelized, and threads from it sending events are getting in race condition for maven listener monitor.
> One possibility would be to implement a "demuxer" listener, that wraps another listener: it receives even from multiple threads events, returns fast, but passes the incoming events on single thread to wrapped listener. This makes resolver relieve a bit, but also keeps actual listener simple, as it can be coded single threaded.



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