You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Steve Loughran <st...@apache.org> on 2006/11/15 16:06:55 UTC
resolution of relative paths in
Sometimes when people ask me what I do for a living, I say "I break
things". Its why I'm so good at what I do: I'm inherently clumsy.
Today I have a project with buildlist
<ivy:buildlist reference="child.projects" skipbuildwithoutivy="true">
<fileset dir="." includes="*/build.xml"/>
<fileset dir="extras" includes="*/build.xml"/>
<fileset dir="components" includes="*/build.xml"/>
</ivy:buildlist>
this includes files which import configurations
<configurations defaultconfmapping="runtime">
<include file="../antbuild/ivy/configurations.xml"/>
</configurations>
This is failing, because the relative path is being resolved in the base
directory, not relative to the ivy file itself.
/home/slo/Projects/SmartFrog/Forge/core/build.xml:358: impossible to
parse ivy file for
/home/slo/Projects/SmartFrog/Forge/core/testharness/build.xml:
ivyfile=/home/slo/Projects/SmartFrog/Forge/core/testharness/ivy.xml
exception=java.text.ParseException: problem occured while parsing ivy
file. message:
/home/slo/Projects/SmartFrog/Forge/core/../antbuild/ivy/configurations.xml
(No such file or directory) in
file:/home/slo/Projects/SmartFrog/Forge/core/testharness/ivy.xml
Defect?
-Steve