You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/04/03 10:59:32 UTC
[jira] Resolved: (IVYDE-45) tag in ivyconf is not
resolved
[ https://issues.apache.org/jira/browse/IVYDE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin resolved IVYDE-45.
-------------------------------
Resolution: Won't Fix
This is not an IvyDE bug, but an Ivy strange way to behave:
https://issues.apache.org/jira/browse/IVY-89
So I mark this issue as won't fix for IvyDE, since it should be fixed in Ivy.
As a workaround, use <properties file="${ivy.conf.dir}/path/to/your/properties/from/your/configuration/file/directory/ivyconf.properties"/>
Hope this helps
> <properties> tag in ivyconf is not resolved
> -------------------------------------------
>
> Key: IVYDE-45
> URL: https://issues.apache.org/jira/browse/IVYDE-45
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
> Environment: Eclipse Version: 3.2.2 Build id: M20070212-133
> IvyDE version 1.2.0 ?
> Reporter: Nikita Salnikov-Tarnovski
>
> In my ivyconf.xml some properties are described using ant propertie placeholders, ${} . In order to resolve them I use
> <properties file="ivy.properties" />
> tag in my ivyconf.xml file.
> From Ant all works just fine. But Eclipse's IveDE cannot resolve relative path to this properties file. If I write full path, /home/user/projects/ etc... it works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.