Hi, I rapidly browsed the thread, please excuse me if I missed something. Isn't mvn dependency:purge-local-repository the solution?
Please note that I'm 100% with people saying releases must never change. And it's so important it's not something specific to maven world. Imagine you release a 1.0 to some client, and try to find the corresponding sources when encountering a blocking bug. You're either going not to be able to find the right sources, or to have to do some ugly thing like storing svn-revision in the MANIFEST while packaging the jar... That's just something that should not be done in the software world, period. Cheers Le 5 août 2010 22:08:03 UTC+2, Wayne Fay <wayne...@gmail.com> a écrit : > > The network traffic that that would cause in a modern project with dozens > of > > dependencies would create a real nuisance. > > If every artifact had md5 and sha1 hashes etc, then the traffic would > merely be to check the hashes against the local artifact... which > Maven already does, and complains when things don't match. > > Note: I'm not encouraging this approach. Releases must never change, > period, end of story. Push another release if you find a given release > is broken. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
