Hi Yann, Yann Andenmatten wrote on Monday, March 06, 2006 2:53 PM:
> Hi, > > I'm surprised that we can deploy a jar again and again without even a > warning (at least using a deploy:deploy-file). My wish would > have been to > receive an error if an artifact is already present in the remote > repository (with the same version). I can get this behavior > if I set the > jar file read-only. But I didn't find a option in the deploy > plug-in to > force this flag during the deploy process. > > In our company, several groups use maven. Some of them are > only using the > repository as a mean to share their jars. They uses the > deploy:deploy-file command. The risk is that they override a previous > version by accident. > > Does anyone face the same problem? That happened to me too. I've been also overwriting released artifacts by accident, when I forgot to reset the version to SNAPSHOT (where this is the desired behaviour). OTOH I also had to redo a release because of some nasty circumstance. So it would be good to enable the overwrite of releases at least by setting a system property. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
