You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Martin Stockhammer (JIRA)" <ji...@apache.org> on 2019/03/10 16:57:00 UTC

[jira] [Closed] (MRM-1749) Delete Released Snapshots Not Working / Expectations?

     [ https://issues.apache.org/jira/browse/MRM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Stockhammer closed MRM-1749.
-----------------------------------
    Resolution: Won't Fix

Versioning scheme is given by maven.

> Delete Released Snapshots Not Working / Expectations?
> -----------------------------------------------------
>
>                 Key: MRM-1749
>                 URL: https://issues.apache.org/jira/browse/MRM-1749
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.3.5, 1.4-M3
>            Reporter: Alex Franken
>            Priority: Major
>
> We have two managed repos (internal & snapshots).  Both have been marked with "Delete released snapshots".  As you would expect, we do not allow snapshots in in "internal" and no releases in "snapshots".  We also use proxy connectors.  I have tried both 1.3.5 & 1.4-M3 without luck.
> I'm wondering if logic requires pre-M3 version conventions (i.e. 1.3-SNAPSHOT & 1.3-RELEASE).  We use a variation which I thought was supported in Maven 3.  For example, 1.0.0.BUILD-SNAPSHOT & 1.0.0.RELEASE.  Could this be the issue?  Can someone provide any detail on the logic used for this feature? A little more about the M3 version changes http://docs.codehaus.org/display/MAVEN/Versioning.  This particular convention was modeled after the Spring Framework (and related Spring projects).
> Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)