It's not. We'd rather fix the problem differently than by exposing the timeouts.
On Fri, Aug 2, 2013 at 11:46 AM, Luke Daley <luke.da...@gradleware.com>wrote: > Is this timeout configurable? > > Begin forwarded message: > > > From: Gradle <noreply.gra...@getsatisfaction.com> > > Subject: New problem: Timeout waiting to lock artifact cache > > Date: 1 August 2013 8:28:06 PM GMT+01:00 > > To: luke.da...@gradleware.com > > > > Gradle > > swpalmer just reported this problem in Gradle: > > Timeout waiting to lock artifact cache > > > > 1.7.-rc-2 > > > > A problem occurred evaluating root project 'MyProject'. > > Could not resolve all dependencies for configuration ':nativesdk'. > > Timeout waiting to lock artifact cache > (C:\Users\me\.gradle\caches\artifacts-26). It is currently in use by > another Gradle instance. > > > > I get the above sometimes when doing many builds on the same machine. > > Is there a way to increase the timeout or something? > > Notify me when people reply REPLY > > This message sent from the Gradle community on Get Satisfaction. > > To unsubscribe or change your email settings, click here. Don't reply > directly to this email. > > > > Create a customer community for your company at GetSatisfaction.com. > > > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware; Lead@mockito
