ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Coene <>
Subject Re: Ivy bugs
Date Fri, 17 Aug 2012 22:39:03 GMT
Hi Danny,

they seems bugs indeed.
However, I think you can workaround them by specifying the 'mapped' attribute in your <conf>
In addition, if Ivy would work correct on this, you should specify this 'mapped' attribute
anyway because this construct doesn't take the value of your defaultconfmapping attribute
into account.


 From: Danny Yates <>
To: Ant Developers List <> 
Sent: Friday, August 17, 2012 2:58 PM
Subject: Ivy bugs

I've just raised a couple of Ivy bugs which strike me as quite serious.
They both involve declaring dependencies using the nested <conf> element
syntax and ending up with either the wrong dependencies delivered or no
dependencies at all!

Is there any chance of getting them looked at in the 2.3.0 timeframe?


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