Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 38119 invoked from network); 11 May 2010 14:48:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 May 2010 14:48:04 -0000 Received: (qmail 2145 invoked by uid 500); 11 May 2010 14:48:04 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 2120 invoked by uid 500); 11 May 2010 14:48:04 -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 2113 invoked by uid 99); 11 May 2010 14:48:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 May 2010 14:48:04 +0000 X-ASF-Spam-Status: No, hits=-1413.2 required=10.0 tests=ALL_TRUSTED,AWL 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; Tue, 11 May 2010 14:48:03 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4BElgtp007467 for ; Tue, 11 May 2010 14:47:43 GMT Message-ID: <2224533.4291273589262900.JavaMail.jira@thor> Date: Tue, 11 May 2010 10:47:42 -0400 (EDT) From: "Phil Clay (JIRA)" To: notifications@ant.apache.org Subject: [jira] Created: (IVY-1191) Allow configuration exclusion for resolve/retrieve/publish/etc MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Allow configuration exclusion for resolve/retrieve/publish/etc -------------------------------------------------------------- Key: IVY-1191 URL: https://issues.apache.org/jira/browse/IVY-1191 Project: Ivy Issue Type: New Feature Affects Versions: 2.1.0 Reporter: Phil Clay Priority: Minor For specifying confs for resolve/retrieve/publish, you can either * explicitly specify confs (e.g. "build,deploy,test"), or * specify all (e.g. "*"), or * specify all public (e.g. "*(public)"), or * specify all private (e.g. "*(private)") All of these work on the principle of inclusion. i.e. only include those configurations I have specified. I would like the ability to select confs based on exclusion. i.e. Include everything, except the ones I have explicitly stated. The reason is that our build process, by default, builds a LOT of stuff. Our developers have the options of turning off certain things to make the builds faster. (For example, our build publishes instrumented artifacts for gathering code coverage data during qa cycles. It would be nice to be able to turn off the "instrumented" conf without having to know how to turn on everything but the "instrumented" conf) I'll propose one option. (There are probably several ways to do this...) In the conf string, use the - character to indicate exclusion. For example: * conf="*,-instrumented" would include everything except the instrumented conf * conf="*(public),-instrumented" would include all public confs except the instrumented conf * conf="build,deploy,test,instrumented,-instrumented" would only include build, deploy, test. I'd like this case to be handled, so we can have a default inclusion string (which may include everything "*", or be a specific list of inclusions "build,deploy,test,instrumented"), but also be able to negate certain confs simply by concatinating an exclusion string "-instrumented". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.