You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Brian Fox (JIRA)" <ji...@apache.org> on 2015/03/07 01:06:38 UTC

[jira] [Commented] (INFRA-7553) Would like karma for deleting old snapshots of Apache SIS

    [ https://issues.apache.org/jira/browse/INFRA-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351174#comment-14351174 ] 

Brian Fox commented on INFRA-7553:
----------------------------------

i think I see the problem. The original message indicates you are trying to delete from the group repository which is always read only. Instead go to the hosted snapshot repository and delete there.

I checked again and your user specifically has the ability to delete sis snapshots.

> Would like karma for deleting old snapshots of Apache SIS
> ---------------------------------------------------------
>
>                 Key: INFRA-7553
>                 URL: https://issues.apache.org/jira/browse/INFRA-7553
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Nexus
>            Reporter: Martin Desruisseaux
>            Assignee: Brian Fox
>            Priority: Minor
>              Labels: #bugbash
>             Fix For: Aug 2014
>
>
> I would like to delete the old snapshots in the http://repository.apache.org/content/groups/snapshots/ repository after Apache SIS release. For example now that our project development switched to 0.5-SNAPSHOT, I would like to delete the 0.4-SNAPSHOT artefacts (or at least the 0.3-SNAPSHOT ones). I tried to login on Nexus, selected "Repositories" > "Snapshots" > "Browse Storage" tab, selected the "org/apache/sis/sis-metadata/0.3-SNAPSHOT" node, selected a file and clicked on "Delete", but got "The server did not delete file/folder from the repository". I tried on different files.
> I'm a SIS PMC member. Is is sufficient for having the right to delete old snapshots, or do I need to proceed in a different way?
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)