Return-Path: 
 <notifications-return-20083-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
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 8BA5F9BB7
	for <apmail-ant-notifications-archive@minotaur.apache.org>;
 Sat, 18 Aug 2012 22:47:38 +0000 (UTC)
Received: (qmail 25653 invoked by uid 500); 18 Aug 2012 22:47:38 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 25615 invoked by uid 500); 18 Aug 2012 22:47:38 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 25607 invoked by uid 99); 18 Aug 2012 22:47:38 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Aug 2012 22:47:38 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 0BD5F2C04AB
	for <notifications@ant.apache.org>; Sat, 18 Aug 2012 22:47:37 +0000 (UTC)
Date: Sun, 19 Aug 2012 09:47:37 +1100 (NCT)
From: "Danny Yates (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <1488753166.27410.1345330058049.JavaMail.jiratomcat@arcas>
In-Reply-To: <947090527.23234.1345207958026.JavaMail.jiratomcat@arcas>
Subject: [jira] [Comment Edited] (IVY-1371) Incorrect artifact resolution
 when using nested <conf> elements
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-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437428#comment-13437428 ] 

Danny Yates edited comment on IVY-1371 at 8/19/12 9:45 AM:
-----------------------------------------------------------

Thanks Maarten. 

My understanding was that breaking an inline conf mapping into <conf> elements was essentially the same as splitting on ';', and then getting the name and mapped attrs was the same as splitting on '->'. Does that make sense?

So

  <dependency conf='a->b;c;d->e' ... />

would be the same as

  <dependency ...>
    <conf name='a' mapped='b'/>
    <conf name='c'>
    <conf name='d' mapped='e'/>

No?

But in the former case the defaultconfmapping would get applied to conf 'c' but it wouldn't in the latter?

It seems to me that the two syntaxes should be semantically identical. We use the latter because we have a lot of confs for building our code. But it does seem to behave logically - at least in my small brain!

Thanks for your time on this. 
                
      was (Author: dty):
    Thanks Maarten. 

My understanding was that break an inline conf mapping into <conf> elements was essentially the same as splitting on ';', and then getting the name and mapped attrs was the same as splitting on '->'. Does that make sense?

So

  <dependency conf='a->b;c;d->e' ... />

would be the same as

  <dependency ...>
    <conf name='a' mapped='b'/>
    <conf name='c'>
    <conf name='d' mapped='e'/>

No?

But in the former case the defaultconfmapping would get applied to conf 'c' but it wouldn't in the latter?
                  
> Incorrect artifact resolution when using nested <conf> elements
> ---------------------------------------------------------------
>
>                 Key: IVY-1371
>                 URL: https://issues.apache.org/jira/browse/IVY-1371
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0, 2.3.0-RC1
>            Reporter: Danny Yates
>         Attachments: build.xml, ivy.xml
>
>
> Please see attached build.xml and ivy.xml
> When resolving the 'transitive' conf, Ivy pulls down Mina, which is not in that conf, and it additionally pulls down Mina's transitive dependencies even though the conf that Mina is in has transitivity turned off.
> If you use the alternative "inline" syntax for conf mapping, this bug doesn't happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira