Nevermind, turned out I didn't have any local builds of "B", so it used our public repo version that doesn't use the replacedynamicrev="false" setting.
Except I thought the force="true" setting would always pull from that repo if there is one. Since I have integration builds of A and C on local, when I rebuild A, shouldn't it still get C off local when it resolves the dependencies for B? -----Original Message----- From: Alex Zhukov [mailto:[email protected]] Sent: Friday, August 14, 2009 10:36 AM To: [email protected] Subject: RE: latest.integration and replacedynamicrev question. Jon, How does B describe C as a dependency? How does A describes B? Can you post your ivy.xml files for A,B and C? Aleksey > Subject: latest.integration and replacedynamicrev question. > Date: Fri, 14 Aug 2009 10:17:24 -0400 > From: [email protected] > To: [email protected] > > Hello, > > I'm having a problem with getting latest.integration to work with some > cases. > > I have projects A, B, C and A depends on B, B depends on C. > > I rebuild C, put it in my local repo (where force="true") Then I rebuild > A. But ivy doesn't get the new version of C. > > Is replacedynamicrev="false" in <ivy:publish> supposed to handle this, > or am I always going to have to rebuild B when I rebuild A? > > Thanks, > Jon > _________________________________________________________________ Get your vacation photos on your phone! http://windowsliveformobile.com/en-us/photos/default.aspx?&OCID=0809TL-H M
