archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EJ Ciramella" <>
Subject RE: Repository Purge By Days Older Than
Date Sat, 30 Aug 2008 15:55:36 GMT
As I posted to the jira, I'll post here and see who can answer this the

How does Archiva determine if something is a snapshot or not?  Is it
because it found 1.0-SNAPSHOT in the path or is it because it finds
1.0-SNAPSHOT within the artifact's pom Archiva is looking at?

We've bent the rules here a bit (and are using deploy:deploy-file) and
while we have released versions (say, 1.0), within that pom, the version
still says 1.0-SNAPSHOT.

I have a working solution for my company (a way to automatically adjust
the internal numbers), so let's not worry about my personal rats nest.

-----Original Message-----
From: Brett Porter [] 
Sent: Saturday, August 30, 2008 1:35 AM
Subject: Re: Repository Purge By Days Older Than

2008/8/30 EJ Ciramella <>

> So I'm correct then Brett?  The only way to purge is to check off the
> repository purge check box on the repository scanning page?

That's correct, but you should note that it *never* purges releases from
repository regardless of what you have configured. It is just for

> If I've misunderstood, please let me know because I want this off
> Otherwise, here's the bug.
> Seems a little short sighted to NOT have each repository track if it
> purges or not (and what's accomplished with each scan).  Why try to
> all that configuration to a single place?

Patches welcome!


Brett Porter

View raw message