Thanks, that's good to know. It actually does help quite a bit since I couldn't find that information anywhere on the website or wiki.
The problem that spurred this question is that we are running into problems with the integration of Hudson-Maven2-Archiva. We perform a build every 30 minutes and if I use the deploy goal for Maven2 on Hudson (or the deploy to repository option), every 30 minutes it adds a new version and updates the SNAPSHOT version. Example at 10:30am 10:00am build - 1.0-20080818.143303-138 10:30am build - 1.0-20080818.150302-139 Latest snapshot: 1.0-SNAPSHOT (actually 1.0-20080818.150302-139). All the version 1.0-YYYYMMDD.TTTTTT-BBB are retained and never purged by Archiva. When I set up repository scanning to purge old files (retention count 5, days 0) it leaves all these old builds. Does anyone know a way to get this setup such that Archiva will actually remove these old versions? Thanks in advance. Alastair -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2008 10:00 AM To: [email protected] Subject: Re: Delete files from Archiva On Mon, Aug 18, 2008 at 9:30 AM, Alastair FETTES <[EMAIL PROTECTED]> wrote: > When I need to manage some of the files in my Archiva 1.1 repository > do I perform this by simply managing them on the disk? An example is > if a number of jar+pom files were added incorrectly and I need to > remove them. Right now the only way to delete is by modifying the filesystem directly. (As a repository manager you should be able to do it through the webdav interface, for examply by opening the repo as a 'web folder' in Windows, but I haven't tried that in a while.) Being able to delete through the web ui has been on my wish list for a while and I just opened an issue yesterday. You might want to comment on/vote for it: http://jira.codehaus.org/browse/MRM-913 -- Wendy
