Uploaded image for project: 'Archiva (Retired)'
  1. Archiva (Retired)
  2. MRM-992

Managed Repository: allow to block deployment of existing release-artifacts

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 1.1.3
    • None
    • repository interface
    • None
    • any

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MRM-747 Archiva should prevent re-deployment of released or non-snapshot versioned artifacts

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. MDEPLOY-74 Add an option to be able to abort if an artifact is already present in the deployment repository

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              wsmoak Wendy Smoak
              axismundi Marc Lustig
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: