Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 40789 invoked from network); 28 Jun 2009 13:05:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Jun 2009 13:05:00 -0000 Received: (qmail 95133 invoked by uid 500); 28 Jun 2009 13:05:11 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 95059 invoked by uid 500); 28 Jun 2009 13:05:11 -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 95050 invoked by uid 99); 28 Jun 2009 13:05:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jun 2009 13:05:11 +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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jun 2009 13:05:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 37B90234C046 for ; Sun, 28 Jun 2009 06:04:47 -0700 (PDT) Message-ID: <1488182883.1246194287227.JavaMail.jira@brutus> Date: Sun, 28 Jun 2009 06:04:47 -0700 (PDT) From: "Xavier Hanin (JIRA)" To: notifications@ant.apache.org Subject: [jira] Resolved: (IVY-1097) configuration groups In-Reply-To: <129025964.1246193087726.JavaMail.jira@brutus> 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-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Hanin resolved IVY-1097. ------------------------------- Resolution: Fixed Fix Version/s: trunk I've just implemented the feature as described here, with a unit test and documentation update. > configuration groups > -------------------- > > Key: IVY-1097 > URL: https://issues.apache.org/jira/browse/IVY-1097 > Project: Ivy > Issue Type: New Feature > Components: Core > Reporter: Xavier Hanin > Assignee: Xavier Hanin > Fix For: trunk > > > In modules having a lot of configurations, sometimes it would be nice to be able to define a group of configurations based on their attributes (including extra attributes). The proposed syntax is {{*[att=value]}} > For instance, one could define an extra attribute named 'axis' on the configuration, and then refer to all configurations where 'axis' is 'platform' with {{*[axis=platform]}}. > Here is an example of Ivy file using this notation: > {noformat} > > module="mod5.1" > revision="4.5" > status="integration" > publication="20090501110000" > /> > > > > > > > > > > > > > > > > > > {noformat} > In this ivy file, {{*[axis=platform]}} is equivalent to {{windows,linux}} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.