>-----Original Message----- >From: Eduardo M KALINOWSKI [mailto:edua...@kalinowski.com.br] > >On Sex, 06 Ago 2010, "Haszlakiewicz, Eric" wrote: >> 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? > >You don't have to, because released artifacts do not change[0]. > >[0]Unless someone intentionally screws up. And it is no accidental >screw up, I think all artifact managers forbid redeploying a non >snapshot version. So in order to that happen, someone must circunvent >the normal deploying route. If someone really needs to do so, then >that person may simply warn everyone that might be affected. That is >feasible, because such situation should never happen in any of the >public repositories, being limited to the organization repository.
It doesn't require much of a screwup to create a changed release artifacts. For example, all it takes is a simple typo when uploading an artifact to your nexus repository. I did exactly this when trying to import a specific release of a package that isn't available on central and isn't built through maven. I ended up with releases in the repository with the wrong jar files attached, and by the time I noticed it was wrong people had already tried to build things using it, and I didn't realize that there was something I needed to warn about. Even if I did warn people, the overhead of everyone needing to read an email, figure out where they ran builds from, figure out what needs to be removed and remove the files from every machine that they might have worked on is huge. i.e. I intended to upload foox-1.2.jar as com.mycompany:foox:1.2 fooy-1.2.jar as com.mycompany:fooy:1.2 but I actually ended up with it switched fooy-1.2.jar as com.mycompany:foox:1.2 foox-1.2.jar as com.mycompany:fooy:1.2 I don't have control over the release cycle of these packages so I couldn't just declare a new release. Even after I fixed our central repository people were having problems building. Eventually we figured out what was going on, but it would have been far easier if maven could have actually told us that there was an inconsistency between the central repo and the .m2 directories. In the real world artifacts DO change. I've seen other people ask about this on the mailing list so I know I'm not the only one that has run into situations like this. eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
