[ 
https://issues.apache.org/jira/browse/IVY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maarten Coene resolved IVY-827.
-------------------------------

    Resolution: Invalid
      Assignee: Maarten Coene

ok, I see it now.
I think you've hit the incompatible change introduced in IVY-372: the relative 
path is now evaluated against the parent settings file, not against the current 
directory anymore.
So, I'm resolving this as invalid since I don't think this is a bug. Please 
reopen if you disagree.

Maarten

> latest development build of SVN repository number 663029 has error in 
> settings file include mechanism
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IVY-827
>                 URL: https://issues.apache.org/jira/browse/IVY-827
>             Project: Ivy
>          Issue Type: Bug
>            Reporter: Shawn Castrianni
>            Assignee: Maarten Coene
>
> I just built the latest ivy code from the trunk and tried it out.  There 
> appears to be a bug in the include mechanism for including one settings file 
> into another.  Below is the bug I am getting.  Notice how the "lgcbuild/ivy" 
> is repeated in the path to the file I am trying to include causing it to not 
> be found.  If I revert back to the previous ivy jar I had (I think beta 2) 
> everything works fine.  I need some of the latest fixes in ivy trunk.  I 
> don't suppose anybody could fix this ASAP??
> /d01/devmani/lgcbuild/ivy/build/master.xml:443: impossible to configure 
> ivy:settings with given file: 
> /d01/devmani/lgcbuild/ivy/release_specs/ivy-DS_5000_0_1_0.xml 
> :java.text.ParseException: failed to load settings from 
> file:/d01/devmani/lgcbuild/ivy/release_specs/ivy-DS_5000_0_1_0.xml: io 
> problem while parsing config file: 
> /d01/devmani/lgcbuild/ivy/lgcbuild/ivy/release_specs/ivy-master.xml (No such 
> file or directory)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to