I got the same problem with ehcache.
In this case, I have a specific <dependency> asking for revision 1.5.+
<dependency org="net.sf.ehcache" name="ehcache" rev="1.5.+">
<artifact name="ehcache" type="jar"/>
<exclude org="org.hibernate"/>
</dependency>
But the same artifact may be requested by implicitly requested by other of
my <dependencies> on Hibernate and Spring
I did not have this problem with 2.0.0
I have trying ading
<exclude org="net.sf.ehcache" name="ehcache"/>
to some of my dependencies
I also tried to add /[type]/ to my retrieve path pattern without success.
On Sun, Jun 6, 2010 at 4:56 PM, Maarten Coene <maarten_co...@yahoo.com>wrote:
> Are you sure that it's not a problem of your retrieve pattern as Ivy
> suggests?
> If this pattern for instance doesn't has the [type] or [classifier] token,
> Ivy will download the source/javadoc artifacts to the same file as the
> regular jar which will give this error.
>
> If however your retrieve pattern is ok, you can try with a snapshot build
> which contains this bugfix.
> You can find the latest snapshot here:
> http://hudson.zones.apache.org/hudson/view/Ant/job/Ivy/
>
> Maarten
>
>
>
>
> ----- Original Message ----
> From: Jorge Medina <cerebrotecnolog...@gmail.com>
> To: ivy-user@ant.apache.org
> Sent: Sun, June 6, 2010 4:33:45 PM
> Subject: Fwd: Multiple artifacts of the module X are retrieved to the same
> file! Update the retrieve pattern to fix this error.
>
> Hello Ivy Users:
>
> I upgraded to Ivy 2.1.0 from 2.0.0 and now I am getting the error when
> retrieving log4j.
>
> impossible to ivy retrieve: java.lang.RuntimeException: problem during
> retrieve of com.example#the-prototype: java.lang.RuntimeException:
> Multiple artifacts of the module log4j#log4j;1.2.13 are retrieved to
> the same file! Update the retrieve pattern to fix this error.
>
> I get a similar error for xalan libraries in another project.
>
> I saw there is a bug (IVY-1148) already filed and that somebody already
> worked on it.
> Is there any release candidate available for download of version 2.2.0 ?
>
> Is there any workaround around the bug? Is the only option to get the
> sources and the patch associated with the bug?
>
> If you have found the same error, did you go back to Ivy 2.0.0 ?
>
> I had decided to upgrade to 2.1.0 because of a bug in 2.0.0 on it that was
> preventing from being to download an artifact. (2.0.0 was unable to
> recognize sha1 signatures generated with openssl or something like that).
> But now I am in a similar position.
>
>
>
> -Jorge
>
>
>
>
>
