[
http://jira.codehaus.org/browse/MRM-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103319
]
Barrie Treloar commented on MRM-294:
------------------------------------
{quote}
Configuration for this should be per repository? Or should it be applicable for
all managed repositories?
{quote}
Good question.
I haven't been following archiva enough to know how remote repositories are
handled differently than internal ones.
But remote repositories can be cleared (as they would be re-obtained if
requested) and internal repositories don't need to have older snapshots around
for very long.
So while per repository makes it easy to customise this feature, I can't really
see what benefit that gives.
It feels like all snapshot repositories could have the same settings.
I'm going to err on the side of over-customization:
The snapshot retention policies should be defined separately to the repo and
when not specified by a repo gets the default retention policy.
> Repository purge feature for snapshots
> --------------------------------------
>
> Key: MRM-294
> URL: http://jira.codehaus.org/browse/MRM-294
> Project: Archiva
> Issue Type: New Feature
> Affects Versions: 1.0-alpha-1
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.0-beta-1
>
>
> We need a way to purge a repository of snapshots older than a certain date,
> (optionally retaining the most recent one) and fixing the metadata.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
