You are viewing a plain text version of this content. The canonical link for it is here.

Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/12/02 16:30:43 UTC

[jira] Resolved: (IVY-654) Share cache with locking

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

Xavier Hanin resolved IVY-654.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-1

I've fixed the remaining issues, and made some real world tests besides the unit test (which is probably more useful since it puts the cache under pretty heavy stress). It seems to work well now, so I mark the issue as resolved.

> Share cache with locking
> ------------------------
>
>                 Key: IVY-654
>                 URL: https://issues.apache.org/jira/browse/IVY-654
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0-beta-1
>
>
> Currently it isn't possible use the same cache from multiple processes. This is a problem in some situations, especially for build servers, which have to use one cache per process, defeating some of the purpose of the cache. Adding an option allowing to use cache locking to ensure the repository cache can be used by concurrent build would be a nice improvement.
> To avoid degrading performance of local builds where the cache is not shared, this should only be an option.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.