If i am not wrong, with unique=false and policy=daily, snaphot updating follows this rules:
1.- Update check (and posibly update itself) is made a day after last publishing in the remote repository of the single artifact being checked. So it could be at any time, any day, and different for every artifact, as they are involved in the current build (not all artifacts at the same time at 12:00 pm, for example). 2.- As said in http://docs.codehaus.org/pages/viewpage.action?pageId=22585, every time a new remote snapshot is published, it will overwrite a local snapshot regardless of age. This is the only way to provide consistent behaviour and avoid clock skew - for example, while it might make sense to honour a local snapshot if it were newer than the remote snapshot, it may be that the local one was built from older sources and so is, in fact, older. For me, this could be very confusing in a team development process (especially 2). I think a deterministic way of snapshot updating is preferable using policiy=never. In this way you always preserve the same snaphots and, eventually, you can use -U to compile with fresh snaphost and get in sync with the team. Of course, you get a deterministic way of snaphot updating at expense of automatic updates, and posibilly, you can discover that one lazy developer has never used -U and is using very old snaphots. Please, any comments are welcome. -- View this message in context: http://www.nabble.com/Deterministic-update-of-snapshots-tp19776315p19776315.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
