[jira] [Commented] (MNG-7599) Include Concurrent Safe Local Repository implementation in standard maven

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634981#comment-17634981 ] 

Michael Osipov commented on MNG-7599:
-------------------------------------

Maven 3.9.0+ will come with a concurrent single JVM lock mechanism by default. Everything else needs to be enabled explicitly.

> Include Concurrent Safe Local Repository implementation in standard maven
> -------------------------------------------------------------------------
>
>                 Key: MNG-7599
>                 URL: https://issues.apache.org/jira/browse/MNG-7599
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Christoph Läubrich
>            Priority: Major
>
> See http://takari.io/book/30-team-maven.html#concurrent-safe-local-repository
> {quote}
> The access to the local repository performed by a standard Maven installation is not designed to support multiple instances of Maven or even multiple threads from the same Maven invocation accessing it concurrently. Concurrent access can end up corrupting the consistency of the repository due to wrong metadata file content and similar problems.
> {quote}
> Multi-Threaded builds are quite common I think and also sharing the same local repository across builds (e.g. builds in the IDE, some long running ones in terminals, even multiple parallel terminals) has several advantages.
> I therefore like to suggest to in cooperate the code into standard maven so one don't need to use extensions for something that users would expect without special configuration.
> The code is  Apache-2.0 license so should be compatible with maven...



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