[ 
https://issues.apache.org/jira/browse/MRM-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471890#comment-17471890
 ] 

Kilian Felder commented on MRM-2028:
------------------------------------

Hi Martin,

The full repository scan is not required. Just create the missing files is 
enough. Afterwards, the standard "repository-purge consumer" of archiva is 
cleaning up the history.

Attached the script 'archiva_history_cleanup' to create the missing files of a 
whole repository (default is 'snapshots') by using the REST service call: curl 
[http://localhost/archiva/restServices/archivaServices/browseService/artifacts/snapshots]

Maybe you can use it too. Btw: The script created 372 missing files in my 
'snapshots' repository.

It would be nice to have something like this directly on the "Repositories 
Administration"-Site as a specific action. Or the full repository scan could do 
this directly. But I think this would be a feature request then.

Now I will check archiva for some weeks to see if everything is working 
correctly. Afterwards I will close this ticket.

Regards, Kilian

[^archiva_history_cleanup]


> CLONE - Purge by retention count deletes files but leaves history on website.
> -----------------------------------------------------------------------------
>
>                 Key: MRM-2028
>                 URL: https://issues.apache.org/jira/browse/MRM-2028
>             Project: Archiva
>          Issue Type: Bug
>          Components: Archiva Components, Web Interface
>    Affects Versions: 2.2.5
>         Environment: Ubuntu 20.04, Tomcat 8.5.71
>            Reporter: Kilian Felder
>            Assignee: Martin Schreier
>            Priority: Minor
>              Labels: features, web-dashboard
>             Fix For: 2.2.8
>
>         Attachments: archiva.log, archiva_2.2.5_bug-1.png, 
> archiva_2.2.5_bug-2.png, archiva_history_cleanup
>
>
> Hi all,
> I'm still having the same issue as described in MRM-1958.
> Files are deleted from the hard drive (as configured in archiva.xml), but the 
> history still exists in the archiva portal.
> Best regards,
> Kilian



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to