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 "Maarten Coene (JIRA)" <ji...@apache.org> on 2006/11/30 13:35:21 UTC

[jira] Commented: (IVY-347) of configurations is incompatible with as paths are resolved relative to the base project

    [ http://issues.apache.org/jira/browse/IVY-347?page=comments#action_12454611 ] 
            
Maarten Coene commented on IVY-347:
-----------------------------------

As temporary workaround, you can work with absolute paths instead of relative paths.

regards,
Maarten

> <include> of configurations is incompatible with <buildlist> as paths are resolved relative to the base project
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-347
>                 URL: http://issues.apache.org/jira/browse/IVY-347
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Steve Loughran
>            Priority: Critical
>
> I can't use the ability to include configurations, even though a shared set of standard configurations is essential.
> why not? Because although I can include a relative configuration, which works from a simple ivy:resolve, when a build file in a parent directory runs a <buildlist> task, the path resolution takes place from this parent project.
> Paths for inclusion must be relative to the ivy.xml file. Marked as critical :)

-- 
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