[
https://issues.apache.org/jira/browse/MRM-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959882#comment-15959882
]
Martin Stockhammer commented on MRM-1838:
-----------------------------------------
No, not by mistake. The 2.2.2 release is coming soon and this feature will not
be included.
The following release will be the 3.0 version with JPA.
I can move this issue to the 3.0.0 release to consider what have to be done for
it.
But looking at the number of active developers at the moment the more realistic
version would be 3.2.0.
If you like to implement it, you are welcome. But you should use the JPA branch
or wait until the JPA branch has been merged into the master.
> Add a time based hold on "delete released snapshots"
> ----------------------------------------------------
>
> Key: MRM-1838
> URL: https://issues.apache.org/jira/browse/MRM-1838
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Sascha Vogt
> Fix For: 3.2.0
>
>
> It would be nice, if the "delete released snapshots" flag could preserve
> recently build snapshots for a while.
> In general the idea is, that when we release an artifact we want to give the
> consumers a few days to update their POMs - If we delete the snapshot right
> away a lot of builds will be failing. It would be nice if one could define a
> number of days where snapshots should still be available (e.g. only delete
> snapshots which are older than e.g. 30 days or so)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
