Changes to the cache aim to tackle some of the cache concurrent-access issues. (e.g. wharf tries to use ivy locking mechanism)
I saw on the mailing list an issue report with cache locks not cleared properly. So I don't think problems are fixed completely. Cheers! On Wed, Aug 3, 2011 at 4:26 PM, Ric Klaren <rkla...@educator.eu> wrote: > Hi, > > On 3 August 2011 10:23, Szczepan Faber <szcze...@gmail.com> wrote: > > Exactly. Plus some other issues we wanted to solve with the new cache > > format. > > Is concurrent access to the cache from multiple builds fixed as well? > I did not recall seeing that on the release notes/milestone 4 fixed > tickets? > > Cheers, > > Ric > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito
