[
https://issues.apache.org/jira/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205923#comment-16205923
]
Kevin Cross commented on MNG-2802:
----------------------------------
Are there any plans to merge the Takari fix for this issue into the standard
Maven release?
I believe this issue may be incorrectly classified as an improvement when it
should be marked as a bug.
When the issue was created it may have been an improvement as CI was less of a
common practice but who would be using Maven now in an enterprise environment
and not doing CI?
There are work arounds for CI systems but if you don't know about this issue
you will not put them in place which will lead to broken builds due to
surprising behaviour by the build tool.
> Concurrent-safe access to local Maven repository
> ------------------------------------------------
>
> Key: MNG-2802
> URL: https://issues.apache.org/jira/browse/MNG-2802
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Stepan Roh
> Assignee: John Casey
> Fix For: Issues to be reviewed for 3.x
>
>
> It seems that access to local Maven repository is not concurrent-safe that is
> multiple Mavens running in parallel may damage contents of local Maven
> repository. It would be a nice improvement, because sharing of local
> repository will lower the need for contacting any other repository. I know
> that Maven proxy can be used, but that adds another layer which may
> unnecessarily stress the machine it runs on.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
