[
https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287265#comment-16287265
]
Per Kristian Fjellby commented on MRM-1967:
-------------------------------------------
FWIW.. We just reported MRM-1966 and it seems to be the exact same problem as
you have. We haven't been able to get the purge to run either.
We've also set up a staging env. running Archiva 2.2.4-SNAPSHOT. As a test, we
rsync'ed over our production repositories and fired up Archiva. Then our
artifacts got purged as expected. If, after a bit more testing, 2.2.4-SNAPSHOT
holds up, we're bumping the production node as well.
That being said. I'd really like to know why it's not working in 2.2.3.
//Per Kristian
> 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
> Attachments: Screen Shot 2017-11-29 at 12.48.11.png
>
>
> 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)
