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 6953EDCD3 for ; Sat, 18 Aug 2012 20:33:38 +0000 (UTC) Received: (qmail 12686 invoked by uid 500); 18 Aug 2012 20:33:38 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 12627 invoked by uid 500); 18 Aug 2012 20:33:38 -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 12614 invoked by uid 99); 18 Aug 2012 20:33: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 20:33:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id F2BC02C04AC for ; Sat, 18 Aug 2012 20:33:37 +0000 (UTC) Date: Sun, 19 Aug 2012 07:33:37 +1100 (NCT) From: "Maarten Coene (JIRA)" To: notifications@ant.apache.org Message-ID: <1069171746.27239.1345322017995.JavaMail.jiratomcat@arcas> In-Reply-To: <947090527.23234.1345207958026.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (IVY-1371) Incorrect artifact resolution when using nested 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=13437404#comment-13437404 ] Maarten Coene commented on IVY-1371: ------------------------------------ The documentation says that if no mapped attribute is specified, it will be mapped to the same configuration as specified with the name attribute. This doesn't seem to work, so this is a bug. A quick look at the parser shows me that in some cases (like yours), the element is completely ignored and your dependency will receive the '%->default' configuration, which could explain your observation. I think we can fix this bug in the 2.3.0 release. Beside this bug, you are requesting a new feature: if the mapped attribute isn't specified, the value of the defaultconfmapping attribute should be considered. This is a new feature request, which will probably not make it into the 2.3.0 release since we are already in the stage of release candidates which means we don't add new features anymore. In addition, this change of default value could break existing ivy files, so we have to think about this in more detail, although I agree that using the defaultconfmapping as default seems like a good idea. > Incorrect artifact resolution when using nested 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