Hi, I have one more feature request, which I consider cruical to improve the consistency of the repository-logic. Before filing another jira feature-request, I'd like to get some feedback.
For snapshots, it's in the nature of the process to overwrite existing versions. By implementing an afterSnapshotDeployment event (in one or another way) one can ensure that snapshots are not added with a new timestamp, but replacing the existing one - independent of the configuration of the maven-deploy-plugin in the project's pom-file. For releases however, AFAIK, Archiva offers no mechanism to prevent overwriting existing release-versions. In my and all of my collegues opinion, this heavily breaks the contract. A release-artifact is supposed to be immutable. It's not just the concept. It has also practical implications for the developers. People download version x from Archiva, some guy wants to do a quick-fix and deploys the artifact as the same version. As a consequence, different developers will have difference editions of this artifact-version in their local repo. What a mess! We had this case a couple of times and people were right to complain that Archiva has not prohibited overwriting the artifact. So, I propose the following logic to get implemented in Archiva. First of all, by default a release-artifact that is already published in Archiva may NOT be overwritten. Furthermore, to provide flexibility for the admins, a new permission property "user may overwrite existing artifacts" should be introduced. Only users that have this permission may overwrite existing artifacts. I think this is a pretty consistent solution. Not quite sure because I don't know the code, but the effort for the implementation seems rather small to me, compared with the benefit. -- View this message in context: http://www.nabble.com/logic-to-prevent-overwriting-release-artifacts-tp25564416p25564416.html Sent from the archiva-dev mailing list archive at Nabble.com.
