Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F1131085F for ; Mon, 8 Dec 2014 15:28:13 +0000 (UTC) Received: (qmail 91829 invoked by uid 500); 8 Dec 2014 15:28:12 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 91779 invoked by uid 500); 8 Dec 2014 15:28:12 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 91769 invoked by uid 99); 8 Dec 2014 15:28:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 15:28:12 +0000 Date: Mon, 8 Dec 2014 15:28:12 +0000 (UTC) From: "Pieter Goddijn (JIRA)" To: notifications@ant.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IVY-1486) Order-dependent resolution: exclude not respected MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IVY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237886#comment-14237886 ] Pieter Goddijn edited comment on IVY-1486 at 12/8/14 3:27 PM: -------------------------------------------------------------- Edit: this patch (both versions) doesnt work completely for our case. The difference is probably that we use a lastest strategy on the main dependency (latest.revision) When usings a specific revision it works, but when using latest it doesnt (the ivy-report task does show the correct version, but the actual delivered ivy.xml doesnt Edit2: i apear to have repsonded to a wrong issue (getting the wrong revisions in deliver, but not related to exclude. was (Author: pvgoddijn@gmail.com): Edit: this patch (both versions) doesnt work completely for our case. The difference is probably that we use a lastest strategy on the main dependency (latest.revision) When usings a specific revision it works, but when using latest it doesnt (the ivy-report task does show the correct version, but the actual delivered ivy.xml doesnt > 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: trunk > Reporter: David Turner > 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 (v6.3.4#6332)