ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Castrianni <>
Subject RE: configuration help
Date Wed, 15 Apr 2009 15:49:06 GMT
I see.  I assumed the wildcard usage was only applicable to the dependency tags where you are
trying to use configurations.  You are saying that configuration declarations themselves can
also use the wildcards.  This should work, however, I still prefer my design.  It just feels
more elegant and powerful by allowing full Boolean operations with configurations (union,
intersection, difference, etc).  But yes, your approach would be less of an impact to others.

Shawn Castrianni

-----Original Message-----
From: Niklas Matthies [] 
Sent: Wednesday, April 15, 2009 5:23 AM
Subject: Re: configuration help

On Wed 2009-04-15 at 04:48h, Shawn Castrianni wrote on ivy-user:
> I suppose that would work, but I think allowing "configuration
> intersection" where a module declares a dependence on the
> intersection of 2 or more configurations of another module is a
> cleaner approach.  Your wildcard approach would require lots of
> configurations for all permutations of all axis to be declared which
> might clutter up the ivy.xml file.

Ok, I skimped over the details. The intent of my approach was exactly
that you wouldn't have to declare all combinations, and instead can
use wildcards when declaring configurations and artifacts. This means
that the set of concrete configurations is potentially open-ended,
yes, because anything matching the wildcards is admissible. The point
of this approach is that it retains the property that dependencies are
still defined just in terms of singular configurations, not
intersections of configurations or whatnot. This likely makes it
easier to implement, would affect less other code and hence be more

-- Niklas Matthies

This e-mail, including any attached files, may contain confidential and privileged information
for the sole use of the intended recipient.  Any review, use, distribution, or disclosure
by others is strictly prohibited.  If you are not the intended recipient (or authorized to
receive information for the intended recipient), please contact the sender by reply e-mail
and delete all copies of this message.

View raw message