You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/10/30 16:32:51 UTC

[jira] Closed: (MRM-992) Managed Repository: allow to block deployment of existing release-artifacts

     [ http://jira.codehaus.org/browse/MRM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak closed MRM-992.
---------------------------

      Assignee: Wendy Smoak
    Resolution: Duplicate

> Managed Repository: allow to block deployment of existing release-artifacts 
> ----------------------------------------------------------------------------
>
>                 Key: MRM-992
>                 URL: http://jira.codehaus.org/browse/MRM-992
>             Project: Archiva
>          Issue Type: New Feature
>          Components: repository interface
>    Affects Versions: 1.1.3
>         Environment: any
>            Reporter: Marc Lustig
>            Assignee: Wendy Smoak
>
> Overwriting existing release-artifacts potentially leads to a great mess, since the previous artifact may already have been downloaded and existing in the local-repos of developer-machines.
> By offering a checkbox "Prevent upload of existing release-artifacts", Archiva should prevent the upload and return an error. As a result, the Maven build-process will fail, which is correct behaviour.
> IMO, the best-practise is, that even a minor bug-fix-version, should NOT have the same major version-number - rather it should result in a completely new (minor) version-number.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira