> My guess is that you only change your artifacts, not your ivy files. And > since the changing pattern checks the publication date of the module > according to the metadata before downloading artifacts, Ivy considers the > module as not updated and trust its cache. I realize this is documented > only > on the dependency tag reference doc for the changing attribute [1], and > not > for the changingPattern. I'll try to improve this. > > Do you use the publish task to publish your changed versions of your > modules?
I do use the publish task and it appears that the ivy.xml is updated in the repository (it has a new publication date). Here's the contents of the repository directory: Volume in drive C has no label. Volume Serial Number is 1EF8-8C94 Directory of C:\temp\ftp\repository\zilliant\policymgt_campaignmanager_swingui\6.5.0.0 02-Nov-07 09:24 <DIR> . 02-Nov-07 09:24 <DIR> .. 20-Nov-07 13:39 1,843 ivy.xml 20-Nov-07 13:39 32 ivy.xml.md5 20-Nov-07 13:39 40 ivy.xml.sha1 20-Nov-07 13:39 147,235 policymgt_campaignmanager_swingui-6.5.0.0.jar 20-Nov-07 13:39 32 policymgt_campaignmanager_swingui-6.5.0.0.jar.md5 20-Nov-07 13:39 40 policymgt_campaignmanager_swingui-6.5.0.0.jar.sha1 20-Nov-07 13:39 193,649 policymgt_campaignmanager_swingui_test-6.5.0.0.jar 20-Nov-07 13:39 32 policymgt_campaignmanager_swingui_test-6.5.0.0.jar.md5 20-Nov-07 13:39 40 policymgt_campaignmanager_swingui_test-6.5.0.0.jar.sha1 20-Nov-07 13:39 37 version-6.5.0.0.properties 20-Nov-07 13:39 32 version-6.5.0.0.properties.md5 20-Nov-07 13:39 40 version-6.5.0.0.properties.sha1 12 File(s) 343,052 bytes 2 Dir(s) 28,347,990,016 bytes free And here's the cache directory: Volume in drive C has no label. Volume Serial Number is 1EF8-8C94 Directory of C:\dev\zpm\main\.ivy_cache\zilliant\policymgt_campaignmanager_swingui 20-Nov-07 15:33 <DIR> . 20-Nov-07 15:33 <DIR> .. 07-Nov-07 17:26 1,843 ivy-6.5.0.0.xml 20-Nov-07 16:35 905 ivydata-6.5.0.0.properties 07-Nov-07 17:26 <DIR> jars 07-Nov-07 17:26 <DIR> propertiess 2 File(s) 2,748 bytes 4 Dir(s) 28,347,883,520 bytes free You can see the timestamp difference and I've diffed the repository's ivy.xml file against the cache's ivy-6.5.0.0.xml file and confirmed that they differ in the publication date. So it does seem strange to me that the Ivy resolution seems happy with the cached version. Chris