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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2006/11/30 13:09:21 UTC
[jira] Created: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
<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
[jira] Commented: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463519 ]
Gilles Scokart commented on IVY-347:
------------------------------------
There is also IVY-89 , which concerns the same problem with the properties tag.
NB: IVY-372 is a duplicate of this one. It add example in the case of the ivyconf.xml is obtained from an http server.
But, IVY-232 is different. It concerns relative path in the ant tasks
> <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
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463638 ]
Xavier Hanin commented on IVY-347:
----------------------------------
IVY-372 is not really a duplicate of this issue: IVY-372 talks about relative path for include element in ivyconf file, this issue talks about include of configurations in an ivy file. Yes I know the word configuration is confusing in Ivy :-)
> <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
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462297 ]
Gilles Scokart commented on IVY-347:
------------------------------------
See also IVY-372 and IVY-232
> <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
> 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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart resolved IVY-347.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0.0-alpha-2
Should be fixed. There is not yet any option to allow the backward compatible mode, but the code is already in place. It will be done in the issue IVY-387.
> <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.0-alpha-2
>
>
> 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.
[jira] Assigned: (IVY-347) of configurations is
incompatible with as paths are resolved relative to the base
project
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart reassigned IVY-347:
----------------------------------
Assignee: Gilles Scokart
> <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
>
> 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.