ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@apache.org>
Subject resolution of relative paths in <buildlist>
Date Wed, 15 Nov 2006 15:06:55 GMT


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

Mime
View raw message