[ 
http://jira.codehaus.org/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126325
 ] 

John Casey commented on MNG-2802:
---------------------------------

To go any further than just ensuring the locking of resolver-status files 
(which are a sort of proto-metadata for the resolver to use that helps track 
unfound artifacts and adhere to an updateInterval for those), we'll need to 
modify the various Wagons, I think. Since these are file-oriented, they manage 
opening, writing to, and closing the files internally. One thing I might be 
able to do is try to manage a file lock on the main artifact file instead of 
the temp file that the wagon is using as its destination (which may not exist, 
so that could complicate things even further). Yet another approach might 
involve creating a lockfile, and managing a lock on that...

I'll look into a couple of these strategies. I don't think it's optimal to bury 
the locking logic in the various wagons, as we're likely to run into 
concurrency problems again and again with each marginal wagon implementation.

> Concurrent-safe access to local Maven repository
> ------------------------------------------------
>
>                 Key: MNG-2802
>                 URL: http://jira.codehaus.org/browse/MNG-2802
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>            Reporter: Stepan Roh
>            Assignee: John Casey
>             Fix For: 2.1
>
>
> 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

        

Reply via email to