ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juha Ranta <juha.ra...@iki.fi>
Subject Getting to the unresolved dependencies from Ant
Date Fri, 16 May 2008 16:43:02 GMT

Hi, 

I'm trying to create a recursive build and publish thing similar to
recursive deliver, except that I'd like like to trigger a new recursive
build for the dependencies that couldn't be resolved. In order to do this
I'd like to get to the unresolved dependencies in one way or another from my
Ant script. That is, when the resolve prints something like this:

[ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: 
[ivy:resolve] :: UNRESOLVED DEPENDENCIES :: 
[ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: 
[ivy:resolve] :: jmx#jmxtools;: not found 
[ivy:resolve] :: red5#jython;2.2: not found 
[ivy:resolve] :: spring#spring-core;2.0.8: not found 
[ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: 

I would like to get to that "spring#spring-core;2.0.8: not found"
information. For example, the artifactproperty task only works with the
actually resolved properties. I noticed that the information I need is in
some resolve-xml-files in the cache with the error "not found", but I don't
know what is the easiest or prettiest way to get to this information. 



-- 
View this message in context: http://www.nabble.com/Getting-to-the-unresolved-dependencies-from-Ant-tp17279215p17279215.html
Sent from the ivy-user mailing list archive at Nabble.com.


Mime
View raw message