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 "Gilles Scokart (JIRA)" <ji...@apache.org> on 2006/11/29 11:39:21 UTC
[jira] Commented: (IVY-89) properties tag in ivy conf so not
support relative path
[ http://issues.apache.org/jira/browse/IVY-89?page=comments#action_12454285 ]
Gilles Scokart commented on IVY-89:
-----------------------------------
See also the thread http://mail-archives.apache.org/mod_mbox/incubator-ivy-user/200611.mbox/%3c455B2D0F.3090505@apache.org%3e
I think there is a choice to make here :
1. The relative path contained in the configuration file are resolved relatively to the basedir of the running project.
2. The relative path contained in the configuration file are resolved relatively to directory containing the configuration file.
3. The relative path contained in the configuration file are resolved relatively to the current execution directory (the current situation).
It is clear from this issue that the choice 3 must be rejected.
I would preffer the choice 2. Indeed, when we have a multi module build, it is not unusual to have only one configuration for the different module. Taken the option 2 allows the configuration to be defined once in the 'root' build of the multiproject and reuse the same configured ivy engine in the build of the sub-module. If we choose the option 1, the configuration will have to be reevalute in every task to be sure that the basedir has not changed.
(NB: See also IVY-232 for issues of relative path in ant tasks)
> properties tag in ivy conf so not support relative path
> -------------------------------------------------------
>
> Key: IVY-89
> URL: http://issues.apache.org/jira/browse/IVY-89
> Project: Ivy
> Issue Type: Improvement
> Environment: eclipse 3.1 jdk 1.4.2
> Reporter: HB
> Assigned To: Xavier Hanin
>
> If in the ivyconf I put a tag
> <properties file="./src/build.properties" />
> it do not work , I get:
> java.text.ParseException: failed to configure with file:/C:/javadev/src/Hermes/ivyconf.xml: problem in config file
> at fr.jayasoft.ivy.xml.XmlIvyConfigurationParser.parse(XmlIvyConfigurationParser.java:65)
> at fr.jayasoft.ivy.Ivy.configure(Ivy.java:259)
> at au.id.oneill.necessitas.core.providers.IvyLibraryProvider.createIvy(IvyLibraryProvider.java:218)
> at au.id.oneill.necessitas.core.providers.IvyLibraryProvider.processDependencies(IvyLibraryProvider.java:148)
> at au.id.oneill.necessitas.core.providers.IvyLibraryProvider.updateAvailableVersions(IvyLibraryProvider.java:86)
> at au.id.oneill.necessitas.ui.NecessitasContainerPage$12.run(NecessitasContainerPage.java:438)
> at au.id.oneill.necessitas.ui.NecessitasContainerPage$13.run(NecessitasContainerPage.java:464)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
> Caused by: java.net.MalformedURLException: no protocol: ./src/build.properties
> at fr.jayasoft.ivy.xml.XmlIvyConfigurationParser.startElement(XmlIvyConfigurationParser.java:140)
> at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1674)
> at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
> at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
> at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
> at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
> at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
> at fr.jayasoft.ivy.xml.XmlIvyConfigurationParser.parse(XmlIvyConfigurationParser.java:59)
> ... 7 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira