>-----Original Message----- >From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On > >On Fri, Aug 6, 2010 at 1:00 PM, Haszlakiewicz, Eric ><ehas...@transunion.com>wrote: > >> Please read the rest of the email thread. The short summary is: >> Yes, I know what *should* happen, but the world isn't perfect and >release >> artifacts DO sometimes change. It is not absurd to be able to detect and >> recover from that kind of situation. >> >> >The solution is to wipe out your local artifact. No one should be updating >released artifacts. If they do, they abused what a release means -- hence >the problem to begin with. The solution given is the only (correct) one in >Maven.
I'm AGREEING with you that the solution is to wipe out the local artifact! But you can only do that once you know there is something wrong. How do you detect that the artifact has changed? Maybe you'll get lucky and something is different enough in your artifact that the build process fails. Or maybe you have some regression testing that you'll do so you notice the problem. Having maven compare the checksums seems like a much more reliable way to catch these problems. eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
