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 "Johannes Stamminger (JIRA)" <ji...@apache.org> on 2007/09/28 11:28:51 UTC
[jira] Created: (IVY-613) Missing configurations with different
version-wildcards dependencies to same dependent version
Missing configurations with different version-wildcards dependencies to same dependent version
----------------------------------------------------------------------------------------------
Key: IVY-613
URL: https://issues.apache.org/jira/browse/IVY-613
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 1.4.1
Reporter: Johannes Stamminger
Priority: Critical
1) with resolving to exactly one version:
moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-[1.5,) in conf U,V
(conf mappings straight forward, U,V->@)
Lates libX version in the repo is e.g. 1.7
We would expect to get 1.7 included in configurations U and V.
But it is included only in U.
2) with resolving to two versions with similar configurations:
moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-1.5 in conf U,V <<< different to 1!
(conf mappings straight forward, U,V->@)
Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.
We would expect to get 1.7 included in configurations U and V.
But it is included only in U.
3) with resolving to two versions with different configurations:
moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-1.5 in conf U,V <<< different to 1!
(conf mappings straight forward, U,V->@)
Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V
Here I'm not sure of the "correct" behaviour ... ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-613) Missing configurations with different
version-wildcards dependencies to same dependent version
Posted by "Jan Koops (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Koops updated IVY-613:
--------------------------
Comment: was deleted
> Missing configurations with different version-wildcards dependencies to same dependent version
> ----------------------------------------------------------------------------------------------
>
> Key: IVY-613
> URL: https://issues.apache.org/jira/browse/IVY-613
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Johannes Stamminger
> Priority: Critical
> Attachments: IVY-613-Test-1.0.zip
>
>
> 1) with resolving to exactly one version:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-[1.5,) in conf U,V
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 2) with resolving to two versions with similar configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 3) with resolving to two versions with different configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V
> Here I'm not sure of the "correct" behaviour ... ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-613) Missing configurations with different
version-wildcards dependencies to same dependent version
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532783 ]
Maarten Coene commented on IVY-613:
-----------------------------------
The test isn't failing when running against current trunk.
> Missing configurations with different version-wildcards dependencies to same dependent version
> ----------------------------------------------------------------------------------------------
>
> Key: IVY-613
> URL: https://issues.apache.org/jira/browse/IVY-613
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Johannes Stamminger
> Priority: Critical
> Attachments: IVY-613-Test-1.0.zip
>
>
> 1) with resolving to exactly one version:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-[1.5,) in conf U,V
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 2) with resolving to two versions with similar configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 3) with resolving to two versions with different configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V
> Here I'm not sure of the "correct" behaviour ... ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-613) Missing configurations with different
version-wildcards dependencies to same dependent version
Posted by "Johannes Stamminger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Stamminger updated IVY-613:
------------------------------------
Attachment: IVY-613-Test-1.0.zip
Test failing due to wrong eviction: libX is told to be evicted in version [1.5,) though this one points to same version resolved on different dependency described by 1.+ and therefore this is no eviction. This leads to libX not being included in configuration deploy.
> Missing configurations with different version-wildcards dependencies to same dependent version
> ----------------------------------------------------------------------------------------------
>
> Key: IVY-613
> URL: https://issues.apache.org/jira/browse/IVY-613
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Johannes Stamminger
> Priority: Critical
> Attachments: IVY-613-Test-1.0.zip
>
>
> 1) with resolving to exactly one version:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-[1.5,) in conf U,V
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 2) with resolving to two versions with similar configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 3) with resolving to two versions with different configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V
> Here I'm not sure of the "correct" behaviour ... ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-613) Missing configurations with different
version-wildcards dependencies to same dependent version
Posted by "Jan Koops (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535930 ]
Jan Koops commented on IVY-613:
-------------------------------
We also have this problem, 2.0.0-alpha1 fixed it.
But with 2.0.0-alpha2 we are at IVY-624 ;-(
> Missing configurations with different version-wildcards dependencies to same dependent version
> ----------------------------------------------------------------------------------------------
>
> Key: IVY-613
> URL: https://issues.apache.org/jira/browse/IVY-613
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Reporter: Johannes Stamminger
> Priority: Critical
> Attachments: IVY-613-Test-1.0.zip
>
>
> 1) with resolving to exactly one version:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-[1.5,) in conf U,V
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 2) with resolving to two versions with similar configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.
> We would expect to get 1.7 included in configurations U and V.
> But it is included only in U.
> 3) with resolving to two versions with different configurations:
> moduleA depends libX-1.+ in conf U
> moduleA depends moduleB in conf U,V
> moduleB depends libX-1.5 in conf U,V <<< different to 1!
> (conf mappings straight forward, U,V->@)
> Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V
> Here I'm not sure of the "correct" behaviour ... ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.