This is an extremely welcome change. As much as I try to educate developers that releases are immutable I still get a few people who try to do it anyway and fail because the artifact is in the local repo or in a proxy.
James On Thu, 2007-10-18 at 22:28 -0700, Jason van Zyl wrote: > I've been working on some release/deployment tools lately for a > client and I modified their deployments so that you could not > accidentally release the same version of an artifact more then once. > I can stop this on the server side only when running a repository > manager, but we have some simple Apache servers that are DAV enables > and someone release an artifact with the same version by mistake and > wreaked havoc for 4 hours. > > I think this one is pretty obvious, I'm not going to write a proposal > I'm just going to fix it because it's not very bright that we allow > the re-release of something that already has been. I'll leave a > option to redeploy if you so choose in the event the driver knows > what he's doing. > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
