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? Yann
