ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <>
Subject Re: transitive dependencies
Date Tue, 12 Jun 2007 07:40:33 GMT

My opinion is that when C changes, if you want A to get the new revision,
the two options are to declare a dependency from A to C (because A requires
a different revision from the one requested by B), which is not my preferred
choice, or publish a new version of B (which is my preferred solution).
Indeed if C has changed it's interesting to rebuild and republish B to make
sure the new version of C doesn't break B. Using a continuous integration
server for this purpose is a very good practice too IMHO.



On 6/12/07, kermitt <> wrote:
> Hi,
> We have for instance 3 modules A, B, C where dependencies are : A->B->C.
> I am working on module C while a team mate is working on A. As we do not
> modify module B, when I release C, B kept previous revision of module C as
> dependency and my team mate do not get the new release.
> What I am going to do to avoid to publish B each time C changed is to put
> a
> dynamic revision 1.0.+ on C dependency in B while disabling replace
> dynamic
> revision in the publish task.
> My concern about this method, I can't ask anymore for specific revision
> and
> break the concept of reproductible build. Can you advice ?
> thx
> --
> View this message in context:
> Sent from the ivy-user mailing list archive at

Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!

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