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 2007/06/20 21:10:26 UTC
[jira] Resolved: (IVY-526) Evicted modules report depends on the
order of the dependencies
[ https://issues.apache.org/jira/browse/IVY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-526.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0.0-alpha-2
I've updated the IvyNode class which seems to fix this problem.
But I wasn't able to create a junit test to reproduce it.
> Evicted modules report depends on the order of the dependencies
> ---------------------------------------------------------------
>
> Key: IVY-526
> URL: https://issues.apache.org/jira/browse/IVY-526
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-1
> Reporter: Gilles Scokart
> Assignee: Maarten Coene
> Fix For: 2.0.0-alpha-2
>
>
> When building ivy from the trunk we should have the commons-httpclient 2.0 evicted by the version 3.0. Indeed, ivy depends on the version 3.0, but commons-vfs depends on the 2.0.
> The build correctly take the version 3.0, but there is no trace of 2.0 being evicted neither on the console, neither in the report.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.