Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 61053 invoked from network); 15 Apr 2009 09:50:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Apr 2009 09:50:50 -0000 Received: (qmail 14348 invoked by uid 500); 15 Apr 2009 09:50:49 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 14287 invoked by uid 500); 15 Apr 2009 09:50:49 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 14277 invoked by uid 99); 15 Apr 2009 09:50:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 09:50:49 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=4356c044d5=shawn.castrianni@halliburton.com designates 34.254.247.12 as permitted sender) Received: from [34.254.247.12] (HELO NP1MAIL002.halliburton.com) (34.254.247.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 09:50:40 +0000 Received: from NP1EXHU012.corp.halliburton.com (np1exhu012.corp.halliburton.com [34.34.132.73]) by NP1MAIL002 (8.14.3/8.14.3) with ESMTP id n3F9oDB5025651 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 15 Apr 2009 04:50:19 -0500 Received: from NP1EXCH012.corp.halliburton.com ([34.34.132.75]) by NP1EXHU012.corp.halliburton.com ([34.34.109.196]) with mapi; Wed, 15 Apr 2009 04:48:33 -0500 From: Shawn Castrianni To: "'ivy-user@ant.apache.org'" Date: Wed, 15 Apr 2009 04:48:32 -0500 Subject: RE: configuration help Thread-Topic: configuration help Thread-Index: Acm9rsQFOky8L0PyQPmO0X32kCNr3wAACjhg Message-ID: <34721A41A7BCF54ABC3B116219A8C1C2056752EE0A@NP1EXCH012.corp.halliburton.com> References: <34721A41A7BCF54ABC3B116219A8C1C2056752EE03@NP1EXCH012.corp.halliburton.com> <20090415094352.GA70411@nmhq.net> In-Reply-To: <20090415094352.GA70411@nmhq.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-HALSTAMP: TRUE X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4,1.2.40,4.0.166 definitions=2009-04-15_05:2009-04-13,2009-04-15,2009-04-15 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0811170000 definitions=main-0904150028 X-Virus-Checked: Checked by ClamAV on apache.org I suppose that would work, but I think allowing "configuration intersection= " where a module declares a dependence on the intersection of 2 or more con= figurations of another module is a cleaner approach. Your wildcard approac= h would require lots of configurations for all permutations of all axis to = be declared which might clutter up the ivy.xml file. --- Shawn Castrianni -----Original Message----- From: Niklas Matthies [mailto:ml_ivy-user@nmhq.net]=20 Sent: Wednesday, April 15, 2009 4:44 AM To: ivy-user@ant.apache.org Subject: Re: configuration help On Tue 2009-04-14 at 17:35h, Shawn Castrianni wrote on ivy-user: > I need something like: win32 client artifacts, linux64 > server artifacts, etc. I essentially need to specify the > intersection of two configuration names and have the artifacts that > only exist in both configurations get resolved. >=20 > Is this possible? I would think this might be a popular enhancement > for those using ivy for native code modules. Maybe a different approach would be to support configuration names with wildcards, like "win32-*" and "*-server". More generally, if there were four axis A-D, one could declare an artifact to be valid for "A-*-C-*", i.e. for any B and D, for example. -- Niklas Matthies ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and pri= vileged information for the sole use of the intended recipient. Any review= , use, distribution, or disclosure by others is strictly prohibited. If yo= u are not the intended recipient (or authorized to receive information for = the intended recipient), please contact the sender by reply e-mail and dele= te all copies of this message.