ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Levy-Lambert (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IVY-1486) Order-dependent resolution: exclude not respected
Date Sun, 02 Dec 2018 13:13:00 GMT

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

Antoine Levy-Lambert resolved IVY-1486.
---------------------------------------
    Resolution: Fixed

The commit by Gintas Grigeliionis on Tuesday August 14 should resolve the issue. It seems
that a new release of ivy is needed though.

> Order-dependent resolution: exclude not respected
> -------------------------------------------------
>
>                 Key: IVY-1486
>                 URL: https://issues.apache.org/jira/browse/IVY-1486
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5.0-rc1
>            Reporter: David Turner
>            Assignee: Antoine Levy-Lambert
>            Priority: Major
>         Attachments: 0001-Fix-IVY-1486.patch, 0001-Make-doesCallersExclude-check-only-callers-of-this-v.patch,
ivy-4sq.xml, ivy-exclude-finagle.xml, ivy-min2.xml
>
>
> To repro, create an  ivy.xml which looks like this (see the attached one for an real-world
example that you can test out):
> dependency A 1.1
> dependency X 1.2
>   exclude Y
> -------
> dependency A 1.1's depends on:
>    dependency X 1.1
> Dependency X 1.1's depends on:
>   dependency Y 1.1
> Dependency X 1.2's depends on:
>   dependency Y 1.2
> ------------------------------
> In this case, we will get Y 1.2.  But if we swap the order of the dependencies in our
ivy.xml, we'll get Y 1.1.  I think 1.1 is correct, because we've excluded 1.2. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message