ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: Probable "configuration" misconfiguration
Date Thu, 03 Apr 2008 18:50:01 GMT
On Thu, Apr 3, 2008 at 8:37 PM, Matt Reynolds <matt.reynolds@qsent.com>
wrote:

> > I suggested to use fallback configurations, which are documented here:
> > http://ant.apache.org/ivy/history/latest-
> > milestone/ivyfile/dependency.html
> > (search for fallback)
>
> In the example given, to enable fallbacks, I'm interpreting the
> documentation to mean I would add a conf of "*->*(*)" to the b2-ivy.xml
> that depends on a ('<dependency org="com.example" name="a" rev="2"
> conf="*->*(*)"/>').
>
> However, that's not working.  Variations on the same theme
> ('default->*(*)') also don't seem to work.  I'm assuming I should only
> have to change the relationship between A2 and B2, since that's what Ivy
> is saying is failing to resolve.  Is that correct?  Can you show me in
> the example where the fallback is supposed to go?

Despite the message, the problem comes from the dependency from b;1 to a;1
with conf="*->foo". So the workaround is to put:
<dependency org="com.example" name="a" rev="1" conf="*->foo(*)"/>

Xavier


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message