ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carr <JamesC...@carfax.com>
Subject RE: Weird dependency resolution errors when resolving maven deps
Date Tue, 08 Feb 2011 14:38:30 GMT
Hi All,

Other things have come to light that might have some bearing on why this happens. It seems
that in this specific example the spring-amqp pom.xml has excluded the sun jars but this seems
to get ignored when resolved through ivy. Adding the exclusions from the pom again myself
in ivy seems to do the trick.

Any idea why this would happen? When using gradle (which afaik uses ivy behind the scenes)
I NEVER have this problem. Another thing is we are using ivy 2.0.0.

Thanks,
James


-----Original Message-----
From: James Carr [mailto:JamesCarr@carfax.com] 
Sent: Wednesday, January 26, 2011 12:56 PM
To: ivy-user@ant.apache.org
Subject: Weird dependency resolution errors when resolving maven deps

Hey All,

I'm trying to configure an existing ivy setup that uses custom confs (jar, war, etc) to pull
down maven dependencies via an http resolver. Currently external dependencies are configured
like this:


		<dependency conf="jar->default" name="spring-context" org="org.springframework" rev="3.0.5.RELEASE"/>

Which seems to work well however once in awhile this will bring in weird dependencies that
I really cannot find in the maven dependency graph for the projects. For example, 

		<dependency conf="jar->default" name="spring-amqp" org="org.springframework.amqp"
rev="1.0.0.M2"/>

will crap out looking for proprietary sun jars (which is weird as they're mentioned nowhere
in the poms) and changing the conf to jar->compile will stop trying to bring those weird
dependencies in, yet avoid resolving other things (such as slf4j).

Any help or pointers would be GREATLY appreciated.


Thanks,
James


Mime
View raw message