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 2007/06/20 20:21:26 UTC

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

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

Gilles Scokart updated IVY-347:
-------------------------------

    Fix Version/s: 2.0

> <include> of configurations is incompatible with <buildlist> as paths are resolved relative to the base project
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-347
>                 URL: https://issues.apache.org/jira/browse/IVY-347
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Steve Loughran
>            Assignee: Gilles Scokart
>            Priority: Critical
>             Fix For: 2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.