ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Melvin" <>
Subject Re: Example of Recursive Delivery?
Date Fri, 19 Sep 2008 18:27:38 GMT
Can anyone comment on this at all?  If I have a module X that depends
on Y, and Y depends on Z - how can I perform a resolve+deliver on X
that goes down to Y and Z?  The best I can do is one level of
dependencies, without getting the "antcall task calling its own parent
target" error.  I must be doing something wrong.  Here is what works
for one level of dependency:

  <target name="deliver-all">
	<property name="ivy.local.default.root" value="repository/local"/>
	<property name="ivy.shared.default.root" value="repository/shared"/>
	<property name="" value="release"/>
	<property name="" value="1.1"/>
    <ivy:resolve file="projects/console/ivy.xml" />
    <ivy:deliver status="${}"
deliverpattern="distrib/ivy-[module]-[revision].xml" module="console"
delivertarget="deliver-dep" />

  <target name="deliver-dep">
    <ivy:resolve inline="true" organisation="${ivy.organisation}"
revision="${dependency.version}" module="${}" />
    <ivy:deliver module="${}"
deliverpattern="distrib/ivy-[module]-[revision].xml" />

But the delivery of the dependency does not deliver the dependency's
dependencies.  And I can't add a delivertarget attribute without
getting an error (I was declaring delivertarget="deliver-dep").  So
how do you normally implement recursive delivery?  (Note I am just
hacking the multi-project sample) in an effort to get this to work.

Finally, would it be reasonable to ask for a property of
"dependency.organisation" to be set as well?  I don't think you can
recursively resolve dependencies with a different organisation without


On Thu, Sep 18, 2008 at 4:24 PM, Mark Melvin <> wrote:
> Hi There,
> I posted earlier about trying to figure out a simple project
> dependency list using ivy:buildlist hacks and after messing around it
> seems that I may want a recursive ivy:deliver instead.  I have managed
> to get this to work for one level of dependencies, but can you truly
> get recursive delivery?  If I call my deliver wrapper, which declares
> itself to be the delivertarget, I get the error "antcall task calling
> its own parent target".  How can it be recursive if it can't call
> itself?  I must be misunderstanding the docs.  Can someone provide an
> example of this?
> Thanks,
> Mark.

View raw message