maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Odea Ching (JIRA)" <>
Subject [jira] Commented: (MRM-294) Repository purge feature for snapshots
Date Thu, 26 Jul 2007 07:08:13 GMT


Maria Odea Ching commented on MRM-294:

Thanks for your comments Barrie :)

Anyway, there was also a discussion regarding this issue and MRM-275 as well in the Archiva
Dev List. I've summarized below what has been agreed upon in the thread. For reference purposes,
the subject of the thread was "Repository purge (MRM-294 and MRM-275)". Please feel free to
add more..

1. Configuration will be for each repository - the repository purge will be implemented as
a consumer, which will be executed during repository scanning. Configuration will be incorporated
on the repository configuration page.
2. Repository purge is configurable in archiva.xml
3. Snapshot retention policies will also be for each repository.

For #3, these are the policies to be implemented:
a. any artifacts that are not in active development will be deleted entirely (eg, 1.0-SNAPSHOT
when 1.0 is released)
b. time based** (e.g. any builds older than 1 month)
c. artifact count retention** (e.g. if user specified "5", then archiva would keep 5 in total
of the latest.. like 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3,
1.1-20070506.121113-4, 1.1-20070506.121113-5 and NOT 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT,

**user will have the option to choose from either of these two criteria

> Repository purge feature for snapshots
> --------------------------------------
>                 Key: MRM-294
>                 URL:
>             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:
For more information on JIRA, see:


View raw message