On Mon, Jun 20, 2011 at 4:29 PM, Jarrod Roberson <[email protected]> wrote:
> I have a highly distributed team and not everyone pays attention to their > emails as good as they should and don't tend to read wiki pages for > comprehension either. > thus returning an error that the -SNAPSHOT version you are trying to publish > is at a release and no longer allowed to be updated would notify them of > their mistake. Archiva already responds with a 409 when you try to deploy a release that already exists (assuming you've turned on that option) so it sounds feasible. Someone more familiar with the code can give you a pointer when they wander by. There's also the idea that developers shouldn't be deploying snapshots at all... only the canonical build environment on the CI server should be allowed to publish, which would also stop it. -- Wendy
