I'll try to take a look at this today. Thanks for the report!
On Tue, Dec 17, 2013 at 8:19 AM, <carsten.pfeif...@gebit.de> wrote: > Hi, > > I just tried the artifact-lock-io lockstrategy with > ivy_2.4.0.alpha_20131214174343.jar. > At some point I got resolve error like this: > > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: UNRESOLVED DEPENDENCIES :: > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: org.hamcrest#hamcrest-core;1.1: > java.nio.channels.OverlappingFileLockException at > sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) > [ivy:resolve] :: org.glassfish#javax.ejb;3.1: > java.nio.channels.OverlappingFileLockException at > sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) > [ivy:resolve] :: org.jboss.weld.se#weld-se-core;1.1.10.Final: > java.nio.channels.OverlappingFileLockException at > sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > > Now I'm wondering if I did something wrong in our <parallel> tasks or if > that rather indicates > a problem in the lock strategy implementation. > > The build system is Debian Linux (Wheezy), filesystem is local. There's no > other access to > Ivy's cache than by Ivy itself. > > Best regards > Carsten
