Major Description
if you publish a module which has a revision in its ivy file :
<ivy-module version="1.2">
<info organisation="myorg" module="foo" revision="1.0"/>
</ivy-module>
Then resolve a module which has a changing dependency on it:
<ivy-module version="1.2">
<info organisation="myorg" module="bar"/>
<dependencies>
<dependency name="foo" rev="latest.integration" changing="true"/>
</dependencies>
</ivy-module>
Then publish again the depency, and then resolve again the master module, the dependency artifact is not updated in cache whereas ivy file is.
The problem comes from the fact that ivy during the publish process of the dependency put the resolved ivy file in cache at the same place it should go when it is resolved by the master module. Consequently, ivy see no changes to the dependency ivy file (same in cache as in repository), and thus doesn't check changes for artifacts.
The solution to this problem is to change the place where ivy store the resolved master ivy file in cache, which should not overlap with dependency ivy files.