[jira] Resolved: (IVY-372) ivyconf include syntax

["Gilles Scokart (JIRA)" <ji...@apache.org>]

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

Gilles Scokart resolved IVY-372.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

The file and the url used in the include tag of the settings is now evaluated relatively to the settings file itself, and not relatively to the current execution directory.

This might intredoce a regression for the build that were using a relative path.  Those build may be fixed by prefixing the relative path by "${user.dir}/" to have the old behavior.

> ivyconf include syntax
> ----------------------
>
>                 Key: IVY-372
>                 URL: https://issues.apache.org/jira/browse/IVY-372
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>         Environment: Any
>            Reporter: Eric Crahen
>            Assignee: Gilles Scokart
>            Priority: Minor
>             Fix For: 2.0-RC1
>
>
> It would be a handy thing if the <include/> tag within an ivyconf.xml could resolve files relative to the file requested, For example,
> I might have a series of ivyconf files:
> http://www.myserver.com/ivy/ivyconf-default.xml
> http://www.myserver.com/ivy/ivyconf-extras.xml
> The only difference between ivyconf-default and ivyconf-extras is that extras adds a different resolver. 
> If possible I'd like to utilize all the stuff in ivyconf-default and not repeat that config in ivyconf-extras.
> Ideally, ivyconf-extras would like sort of like this.
> <ivyconf>
>   <include file="ivyconf-default.xml"/>
>   <resolvers>
>     <!-- New resolvers -->
>   <resolvers/>
>   <!-- Additional property -->
> </ivyconf>
> Now when I ivy:configure url="http://www.myserver.com/ivy/ivyconf-extras.xml", what would 
> be nice would be for ivy to look at the include and say, I'm going to resolve that against the
> path of the config file I'm processing, rather than resolve against the local filesystem; so it
> would use http://www.myserver.com/ivy/ivyconf-default.xml from the remote server.

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