You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Cédric Damioli (Jira)" <ji...@apache.org> on 2019/09/23 16:18:00 UTC
[jira] [Commented] (IVY-1608) Ivy fails incorrectly with evicted
modules with different confs
[ https://issues.apache.org/jira/browse/IVY-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936005#comment-16936005 ]
Cédric Damioli commented on IVY-1608:
-------------------------------------
Attached in a test case to reproduce the issue.
> Ivy fails incorrectly with evicted modules with different confs
> ---------------------------------------------------------------
>
> Key: IVY-1608
> URL: https://issues.apache.org/jira/browse/IVY-1608
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.4.0, 2.5.0-rc1
> Reporter: Cédric Damioli
> Priority: Major
> Attachments: ivy-2.4.x.patch
>
>
> When a module's revision with two confs A and B is evicted by another revision with only conf A, the resolve engine fails complaining that conf B is missing.
>
> Note that this description is strictly the same than the 11-years old IVY-681, which has been promptly fixed but somehow broken in the meantime (maybe while fixing IVY-861).
> There is a test case supposed to handle this case (ResolveTestCase#testEvictWithConf3), but for an unknown reason it always succeed whereas it should not !
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)