I was using the metdata-updater at one time, but we started to see stange issues with the buld number being reset when we do a deploy, even though the build number should have been 35, it became 1. I thought this consumer might be the cause.
-----Original Message----- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:29 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? Currently, I have the following enbled: * create-missing-checksums * index-content * repository-purge * repository-purge * validate-checksums -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:24 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/
