[
https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293203#comment-16293203
]
Martin Stockhammer commented on MRM-1967:
-----------------------------------------
The group is a persistent parameter that is part of the artifact identifier and
should reference the group of artifacts.
E.g. you should set the groupId element to something like:
{{<groupId>de.globis</groupId>}}
Then, when you deploy into a snapshot repository, the version (in the pom.xml)
should always end with '-SNAPSHOT', e.g. 10.3.12-SNAPSHOT
When your artifact is published with the command above, then there should be an
artifact created that has a version like
10.3.12-20171215.202503-4
These are snapshot artifacts and the purge process does only delete artifacts
that have such a version number. All other artifacts are ignored.
> Purge snapshot repository
> -------------------------
>
> Key: MRM-1967
> URL: https://issues.apache.org/jira/browse/MRM-1967
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 2.2.3
> Reporter: Pascal Jacob
> Assignee: Martin Stockhammer
> Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml,
> artifact-listing.txt, globis-solutions-10.3.12-1.pom.xml
>
>
> Hello,
> I have a snapshot repository with following settings:
> - cron = 0 0 * * * ?
> - days older = 0
> - retention count = 1
> - snapshots = true
> - scanned = true
> - delete released snapshots = true
> Artifact filetype = rar
> Repository scanning consumers:
> - repository-purge = true
> But nothing is purged. Nothing is cleaned up. Not even when starting
> directory indexing manually (UI).
> Any ideas what could be wrong?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
