You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Gilles Scokart (JIRA)" <ji...@apache.org> on 2008/07/20 12:14:31 UTC

[jira] Resolved: (IVY-573) Ivy causes IveDE to fail where a properties file is relative to ivyconf.xml

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

Gilles Scokart resolved IVY-573.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

Beter late than never...  This is now fixed.

Thanks a lot for your contribution.  I coult unfortunately not reuse the code, but I have taken your unit test (after adaptation to the lates code base).



> Ivy causes IveDE to fail where a properties file is relative to ivyconf.xml
> ---------------------------------------------------------------------------
>
>                 Key: IVY-573
>                 URL: https://issues.apache.org/jira/browse/IVY-573
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>         Environment: Eclipse 3.2, IvyDE 1.2.0, Ivy 1.4.1, Windows XP, Java 1.5.0_10
>            Reporter: jamie burns
>             Fix For: 2.0-RC1
>
>         Attachments: ivyconf-properties-relative-to-ivyconf.xml.patch.txt, XmlIvyConfigurationParser.java.patch.txt, XmlIvyConfigurationParserTest.java.patch.txt
>
>
> The issue manifests in IvyDE but lve confirmed it to be an Ivy issue. IvyDE fails to create a classpath container where ivyconf.xml has to resolve a properties file that is relative to ivyconf.xml. This occurs because Ivy only tries to resolve the properties file in the current directory. In the case of Eclipse+IvyDE the current directory is the eclipse.exe directory. So the following ivyconf.xml will cause IvyDE to fail.
> <ivyconf>
>    ...
>    <properties file="local.properties" ... />
>    ...
> </ivyconf>
> (This will not fail if build.properties is in the same directory as eclipse.exe)
> I have created a patch which l hope l can attach to this issue.

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