From notifications-return-15072-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org Wed Jan 05 10:56:11 2011 Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 64111 invoked from network); 5 Jan 2011 10:56:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jan 2011 10:56:11 -0000 Received: (qmail 33827 invoked by uid 500); 5 Jan 2011 10:56:11 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 33749 invoked by uid 500); 5 Jan 2011 10:56:10 -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 33742 invoked by uid 99); 5 Jan 2011 10:56:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 10:56:09 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 10:56:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p05AtjdG025155 for ; Wed, 5 Jan 2011 10:55:45 GMT Message-ID: <18794442.157981294224945448.JavaMail.jira@thor> Date: Wed, 5 Jan 2011 05:55:45 -0500 (EST) From: "Chi Lang (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVY-742) Support ivy.xml parent mechanism MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVY-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977728#action_12977728 ] Chi Lang commented on IVY-742: ------------------------------ This look great. Any reason why is not included in the inheritance ? >From my experience, it is as repetitive as , e.g. most module will have standard jar, javadoc, source artifacts. > Support ivy.xml parent mechanism > -------------------------------- > > Key: IVY-742 > URL: https://issues.apache.org/jira/browse/IVY-742 > Project: Ivy > Issue Type: New Feature > Components: Core > Environment: Any > Reporter: Neil Lott > Assignee: Maarten Coene > Fix For: 2.2.0-RC1 > > Attachments: extendsIvyFile-ivy-r709181.patch, extendsIvyFile-ivy-r920176.patch > > > Here's the email that details this feature: > On Thu, Feb 21, 2008 at 11:22 PM, Neil Lott > wrote: > Let's say I have multiple modules each with their own ivy.xml > > > > > > > > conf="interface" ext="jar"/> > > > conf="interface->server"/> > > > and I want them all to share an inherited configuration found in a > file: included-configurations.xml > > > > > > > so in the inherited configurations file I'd also like to include a > dependency that goes along with that configuration. > Is something like this possible? > No, this is not possible in Ivy, but you can use text or xml processing > tools to recompose your Ivy file before asking Ivy to resolve the > dependencies of your module. > Alternatively, since what you ask is close to maven 2 parent mechanism, I > think it could be a nice addition to Ivy feature set. So feel free to open > an issue, and even provide a patch :-) > Xavier > Thanks, > Neil > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.