[
http://jira.codehaus.org/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238118#action_238118
]
John Lonergan commented on MNG-2802:
------------------------------------
This issue really impacts our ability to run concurrent continuous integration
builds making out CI take several times longer to cycle than we'd like. We have
compensated by having each CI task have it's own private local repo but this
massively expands the disk requirements and has the affect of slowing
everything down due to all the duplicate file downloading going on. But the
really painful thing is that when we have separate local repo's the various
threads cannot share the snapshots via the local repo.
Please try to get a fix in place for this.
> Concurrent-safe access to local Maven repository
> ------------------------------------------------
>
> Key: MNG-2802
> URL: http://jira.codehaus.org/browse/MNG-2802
> Project: Maven 2 & 3
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
