It seems like a similar issue in that the problem seems to be caused by using ../ in the path. I can't say for sure that they are related because the presence of ../ itself doesn't make it fail. /foo/../bar works, where /foo/../bar/../baz fails in my example. I will open a JIRA issue.
-Jonathan On Sat, Jan 29, 2011 at 5:52 AM, Maarten Coene <maarten_co...@yahoo.com>wrote: > Seems like a bug... > > Maybe it is related to this issue? > https://issues.apache.org/jira/browse/IVY-582 > > > Maarten > > > > > ----- Original Message ---- > From: Jonathan Williams <spamhammer1...@gmail.com> > To: ivy-user@ant.apache.org > Sent: Sat, January 29, 2011 2:00:51 AM > Subject: Valid Path does not work for Filesystem Resolver > > Hi all, > > I'm using Ivy 2.2.0 in my current project. I've specified a filesystem > resolver and I was playing around with how the root directory to look under > for the ivy and artifact patterns is derived. Through playing around with > the path, I encountered some odd/buggy behavior where I could specify a > valid path but would fail to resolve the file. > > <ivysettings> > <properties file="../../properties/path.properties"/> > <property name="repo.dir" value="${filesystem.repo.root}"/> > > <resolvers> > <filesystem name="local" m2compatible="true"> > <ivy pattern="${repo.dir}/[organisation]/[module]/ivy.xml"/> > <artifact > pattern="${repo.dir}/[organisation]/[module]/[artifact].[ext]"/> > </filesystem> > </resolvers> > </ivysettings> > > path.properties is a file generated by a script prior to building. > Originally I was hardcoding the value for ${filesystem.repo.root} in the > generating script, but I wanted to start deriving the path. When I > generated > the path, the resolve suddenly started failing. However, at the command > line, I was able to copy the jar and ivy file from the repo manually using > 'cp' and the output of the failed call to ivy:retrieve, meaning the path > was > valid, but the resolve was failing. > > module not found: org.slf4j#slf4j;1.6.1 > [ivy:retrieve] ==== local: tried > [ivy:retrieve] > > /opt/workspace/ums/UMS/main/build/developer/../.cache/../../../lib/org/slf4j/slf4j/1.6.1/ivy.xml > > [ivy:retrieve] -- artifact org.slf4j#slf4j;1.6.1!slf4j.jar: > [ivy:retrieve] > > /opt/workspace/ums/UMS/main/build/developer/../.cache/../../../lib/org/slf4j/slf4j/1.6.1/slf4j-1.6.1-jar.jar > > > However, a path like > > /opt/workspace/ums/UMS/main/build/developer/../../../lib/org/slf4j/slf4j/1.6.1/ivy.xml > > resolves just fine and my build works. > > The same behavior holds true if I specify the path directly in the ivy and > artifact pattern, so it isn't an issue with the path.properties file. > > I can work around this easily enough, but I was wondering if others could > reproduce this behavior and if I should I open a JIRA issue to track this? > > Thanks, > > -Jonathan > > > > >
