Good point Niklas. However, I would say that this is unreliable at best when used across repositories; it would probably be okay if all publishing to any of the repositories was always done from the CI server, for instance, so that the publication date is more or less guaranteed to be consistent, but when dealing with local repositories as most people have been doing, this is not the case.
However, if your developers' machines and servers are all synched to a time server then you should be fine using the latest-time strategy. Doug Glidden (703) 317-7523 http://dougglidden.blog.boeing.com -----Original Message----- From: Niklas Matthies [mailto:[email protected]] Sent: Wednesday, October 21, 2009 10:11 To: [email protected] Subject: Re: dynamic revision and determine the most recent On Wed 2009-10-21 at 08:40h, Glidden, Douglass A wrote on ivy-user: > Ivy uses ONLY the revision numbers to compare versions across > repositories-it does not use the "publication date" or any other > metadata Um, doesn't the latest-time strategy do exactly that (using the file time)? (http://ant.apache.org/ivy/history/latest-milestone/concept.html#latest) > -it would be essentially meaningless, since there is no guarantee that > any given server or your local computer has a correctly synchronized > system clock. If an artifact is found with the same revision in two > different repositories, they are assumed to be the same and whatever > repository is first in the chain will be used. So in your case, Ivy > finds that the most recent version in each repository is 1.1.7.1; > since they are the same, it then proceeds to download from the first > repository in the chain. If two revisions are different they need to > have different revision numbers. -- Niklas Matthies
