On Aug 6, 2010, at 6:16 PM, Ron Wheeler wrote: > On 06/08/2010 5:56 PM, Haszlakiewicz, Eric wrote: >>> -----Original Message----- >>> From: Ron Wheeler [mailto:rwhee...@artifact-software.com] >>>> 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? >>> If you can not deploy the release, that will tell you that you are >>> trying to rerelease an artifact. >>>> Maybe you'll get lucky and something is different enough in your >>>> artifact that the build process fails. >>> Your attempt to deploy will fail. That will tell you right away that >> you >>> are doing the wrong thing. >> No, the deployment of a project that USES a changed artifact will NOT >> fail. > > Yes. > That is why releases can not be replaced. > In your case, you should have deleted the wrong artifacts and loaded them > with new versions. > And informed the victims that they needed to update their dependencies. > > You were completely in control of the versions and names.
And, frustrating though it is, that's what I've done when my bad QC has released bad stuff onto Central. You just put out another version and apologize on the web page. There's not a lot else to do, and it's not that bad. -K --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
