ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Williams <>
Subject Valid Path does not work for Filesystem Resolver
Date Sat, 29 Jan 2011 01:00:51 GMT
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.

<properties file="../../properties/"/>
<property name="repo.dir" value="${filesystem.repo.root}"/>

<filesystem name="local" m2compatible="true">
                <ivy pattern="${repo.dir}/[organisation]/[module]/ivy.xml"/>
</ivysettings> 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]       -- artifact org.slf4j#slf4j;1.6.1!slf4j.jar:

However, a path like
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 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?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message