Return-Path: 
 <ivy-user-return-5652-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 95709 invoked from network); 28 Jul 2009 14:14:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 28 Jul 2009 14:14:01 -0000
Received: (qmail 60922 invoked by uid 500); 28 Jul 2009 14:15:18 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 60864 invoked by uid 500); 28 Jul 2009 14:15:18 -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 60854 invoked by uid 99); 28 Jul 2009 14:15:18 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 14:15:18 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [213.73.82.19] (HELO nmhq.net) (213.73.82.19)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 14:15:09 +0000
Received: from matthies by abode.nmhq.net with local (Exim 4.69 (FreeBSD))
	(envelope-from <ml_ivy-user@nmhq.net>)
	id 1MVnS4-000Pph-Ei
	for ivy-user@ant.apache.org; Tue, 28 Jul 2009 16:14:48 +0200
Date: Tue, 28 Jul 2009 16:14:48 +0200
From: Niklas Matthies <ml_ivy-user@nmhq.net>
To: ivy-user@ant.apache.org
Subject: Re: multiple artifact confs: wanting AND instead of OR
Message-ID: <20090728141448.GA86225@nmhq.net>
Mail-Followup-To: ivy-user@ant.apache.org
References: <1fb30820907271319x45e3485fx446e347bc2a90e8f@mail.gmail.com>
 <34721A41A7BCF54ABC3B116219A8C1C2057EC48FC8@NP1EXCH012.corp.halliburton.com>
 <1fb30820907271446x3bd046c6geeb79c4da53fce5a@mail.gmail.com>
 <34721A41A7BCF54ABC3B116219A8C1C2057EC48FD0@NP1EXCH012.corp.halliburton.com>
 <1fb30820907271604xb92b0cet1be358bba1a96c66@mail.gmail.com>
 <34721A41A7BCF54ABC3B116219A8C1C2057EC48FD5@NP1EXCH012.corp.halliburton.com>
 <7916a6a60907272117j54c2884tef4e0b69a3d033ec@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7916a6a60907272117j54c2884tef4e0b69a3d033ec@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 4.11-STABLE i386
X-Editor: VIM - Vi IMproved 6.4
X-Virus-Checked: Checked by ClamAV on apache.org

On Mon 2009-07-27 at 21:17h, Mitch Gitman wrote on ivy-user:
:
> The problem is you can't specify the intersection on the artifacts:
>   <artifact name="mocha-short-hot" type="jar" conf="mocha+short+hot" />
> 
> The onus is on the consumer (the dependent Ivy module) to specify the
> intersection and not the union.

Which, by the way, is dangerous, because the published module has no
way to specify which intersections are expected to work and which
don't. It's a bit analogous to intersecting two class implementations
because you only need their common interface, and hoping that this
intersection still works in any sensible way.

It also doesn't scale to transitive dependencies, see:
http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200904.mbox/%3c20090415170945.GC68410@nmhq.net%3e


Personally I wonder what the actual use cases are of having artifacts
that are only valid for a particular combination of configurations,
where an explicit combination configuration or separate modules
wouldn't be a better solution. The cute pet or the coffee drink
examples don't make any sense to me. ;)

-- Niklas Matthies