Hello, Thanks Stephen for that writeup. It is a good read. For my taste it over-emphasises the moving ground problem. I mean when cooperating with larger projects and lots of developers you get all kinds of problems, but beeing affected by breaking changes of updating snapshots - I cant remember to ever experience that. In fact when SNAPSHOTs change in a severe way it is most likely that I have waited for it, I manually refreshed the dependencies and I am actually happy to see the changes as early as possible (before integrating into a system which isnt working since days and only my old snapshots hide this from me).
But having said that, I also do enjoy an environment with releasing often. This allows each team to decide when to pull in which (released) changes, and this indeed lowers the frequency of broken builds (however it also encourages developers to wait too long with the integration, if you dont nudge them with deoendency upgrade reports). Gruss Bernd Am 03.11.2014 10:39 schrieb "Stephen Connolly" < stephen.alan.conno...@gmail.com>: > Well I knew I'd written something on that topic... but re-reading I am > surprised at how much information I managed to cram in there without it > feeling over dense (for me) > > BTW I am of the *never deploy -SNAPSHOTs* camp but I recognise that there > are other people out there... and I have to interact with them some times > and that post is helpful to explain things to them! > > On 3 November 2014 01:57, Barrie Treloar <baerr...@gmail.com> wrote: > > > On 29 October 2014 20:18, Stephen Connolly < > > stephen.alan.conno...@gmail.com> > > wrote: > > > > > > > > > > > http://developer-blog.cloudbees.com/2012/12/should-you-deploy-snapshots.html > > > > > > Thanks for writing that up! > > I'll remember to point people there instead of having to remember > > half-baked stuff and type :) > > > > This is a useful piece of advice > > "especially in conjunction with the Versions Maven Plugin > > <http://mojo.codehaus.org/versions-maven-plugin/lock-snapshots-mojo.html > > > > which > > has goals for “locking” and “unlocking” your -SNAPSHOT dependencies to > the > > current timestamp version, thereby removing uncertainty. " > > It will allow you to live dangerously on shifting sands and then when you > > get sucked under to go back and lock to a working version. > > But I still think you are better off avoiding that problem in the first > > place. > > >
