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 4D4F99E3C for ; Mon, 4 Jun 2012 18:44:24 +0000 (UTC) Received: (qmail 34457 invoked by uid 500); 4 Jun 2012 18:44:23 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 34352 invoked by uid 500); 4 Jun 2012 18:44:23 -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 34245 invoked by uid 99); 4 Jun 2012 18:44:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 18:44:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 4DB8F142864 for ; Mon, 4 Jun 2012 18:44:23 +0000 (UTC) Date: Mon, 4 Jun 2012 18:44:23 +0000 (UTC) From: "Stephane Bailliez (JIRA)" To: notifications@ant.apache.org Message-ID: <1644563677.35626.1338835463320.JavaMail.jiratomcat@issues-vm> In-Reply-To: <239693223.35618.1338835463090.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (IVY-1356) ivy descriptors are merged incorrectly 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-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Bailliez updated IVY-1356: ----------------------------------- Description: I'm making use of parent definition in ivy files to define general dependencies and configuration across projects. Parent file is typically something like: {code} {code} Ivy file for the project is typically: {code} {code} The result end up being a merge which is incompatible with the schema since dependency and exclude end up being mixed when the file is delivered: {code} conf="default->api;newrelic->default"/> {code} was: I'm making use of parent definition in ivy files to define general dependencies and configuration across projects. Parent file is typically something like: {code} {code} Ivy file for the project is typically: {code} {code} The result end up being a merge which is incompatible with the schema since dependency and exclude end up being mixed when the file is delivered: {code} conf="default->api;newrelic->default"/> {code} > ivy descriptors are merged incorrectly > -------------------------------------- > > Key: IVY-1356 > URL: https://issues.apache.org/jira/browse/IVY-1356 > Project: Ivy > Issue Type: Bug > Components: Core > Affects Versions: 2.2.0 > Reporter: Stephane Bailliez > > I'm making use of parent definition in ivy files to define general dependencies and configuration across projects. > Parent file is typically something like: > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd" > xmlns:m="http://ant.apache.org/ivy/maven"> > > > > > > > > > > > > > > > > > {code} > Ivy file for the project is typically: > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd" > xmlns:m="http://ant.apache.org/ivy/maven"> > > > > > > > > > > > > > > > > {code} > The result end up being a merge which is incompatible with the schema since dependency and exclude end up being mixed when the file is delivered: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > conf="default->api;newrelic->default"/> > > > {code} -- 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