ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Commented: (IVY-844) Add hook for setting RelativeUrlResolver implementation in IvySettings
Date Thu, 19 Jun 2008 21:21:45 GMT


Maarten Coene commented on IVY-844:

I've checked the code and the Ant properties should be expanded.
Could you check again to make sure the ${repository} property is set?
If that seems ok, could you post the relevant parts of your build.xml file?

> Add hook for setting RelativeUrlResolver implementation in IvySettings
> ----------------------------------------------------------------------
>                 Key: IVY-844
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Arthur Branham
>             Fix For: 2.0-RC1
> IvySettings.getRelativeUrlResolver always returns a new NormalRelativeUrlResolver.  I
would like to see a hook made available to set a custom implemenatation of the url resolver,
whether it be setting a thread safe reusable instance or a factory to create a new instance
for each use.
> My interest in this comes from the fact that ant properties are not expanded in dependency
module descriptors.  I have module descriptors which import their configurations from a common
location.  The path of that location will be OS specific based on where Ivy is running.  I
would therefor need a custom relative url resolver which expands properties before constructing
a URL object as done in the NormalRelativeUrlResolver.
> The following is possible right now, but would not work if running from windows.
> <configurations>
> <include file="/repository/org/mod/rev/etc/ivyconfigurations.xml" />
> </configurations>
> An ideal fix for the problem would be:
> <configurations>
> <include file="${repository}/org/mod/rev/etc/ivyconfigurations.xml" />
> </configurations>

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

View raw message