Return-Path: 
 <ivy-user-return-8028-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-ivy-user-archive@www.apache.org
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3C64E76A5
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Tue, 26 Jul 2011 17:25:57 +0000 (UTC)
Received: (qmail 7260 invoked by uid 500); 26 Jul 2011 17:25:56 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 7166 invoked by uid 500); 26 Jul 2011 17:25:56 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 7158 invoked by uid 99); 26 Jul 2011 17:25:55 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 17:25:55 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of sprior@geekster.com
 designates 99.153.139.110 as permitted sender)
Received: from [99.153.139.110] (HELO geekster.com) (99.153.139.110)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 17:25:49 +0000
Received: from [192.168.0.6] (stevepad [192.168.0.6])
	by  geekster.com (8.12.1/8.12.1) with ESMTP id p6QGPOK9001273
	for <ivy-user@ant.apache.org>; Tue, 26 Jul 2011 12:25:25 -0400
Message-ID: <4E2EF87D.8010205@geekster.com>
Date: Tue, 26 Jul 2011 13:25:17 -0400
From: Steve Prior <sprior@geekster.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: Re: container supplied jars excluded in ivy
References: <4E2C3644.8030109@geekster.com> <5255155122564238197@unknownmsgid>
 <4E2C684B.3010105@geekster.com>
 <CAJCKp86gPe5DfAxUiFgP32Li1tZ0gH7HATnKKaQXb618eoRFhQ@mail.gmail.com>,<4E2E15CD.6070906@geekster.com>
 <B54239B8E6758C4A9A59103AD9C359FA10508F55D4@MAILBOXSERVER.add0.masergy.com>
 <4E2E335B.6060500@geekster.com> <4E2EC1BD.4010401@masergy.com>
In-Reply-To: <4E2EC1BD.4010401@masergy.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> I can see how, given your situation, using excludes is a more general solution.
> I guess I'm fortunate not to be in that situation, though I'm glad to learn of
> the per-conf exclude at the <dependencies> level; I wasn't previously aware it
> could be used like that.

Yeah, I just found that <dependencies> level exclude this weekend after opening 
this thread and it's a big step in the right direction.  This feature is 
apparently new to version 2.*.  Would have been even better if the include 
directive had worked there so I could externalize it.

I hope this discussion has/will help others work this out.

Steve