It's by the path. You'll find the incompatibilities between the POM and path in your reports section to tell you which POMs should be corrected in the releases repository. Cheers, Brett
2008/8/31 EJ Ciramella <[EMAIL PROTECTED]> > As I posted to the jira, I'll post here and see who can answer this the > fastest. > > 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 [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 30, 2008 1:35 AM > To: [email protected] > Subject: Re: Repository Purge By Days Older Than > > 2008/8/30 EJ Ciramella <[EMAIL PROTECTED]> > > > 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 > the > repository regardless of what you have configured. It is just for > snapshots. > > > > > > > > If I've misunderstood, please let me know because I want this off > ASAP. > > > > Otherwise, here's the bug. > > > > http://jira.codehaus.org/browse/MRM-930 > > > > 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 > push > > all that configuration to a single place? > > > Patches welcome! > > Cheers, > Brett > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > -- Brett Porter Blog: http://blogs.exist.com/bporter/
