archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Chaffee" <>
Subject RE: archiva-1.0.2 eta?
Date Thu, 20 Mar 2008 04:32:42 GMT
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 [] 
Sent: Wednesday, March 19, 2008 9:29 PM
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 [] 
Sent: Wednesday, March 19, 2008 9:24 PM
Subject: Re: archiva-1.0.2 eta?




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?





On 14/03/2008, Jason Chaffee <> 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



>  -metadata.xml]: Invalid path to Artifact: filename format is invalid,




Brett Porter


View raw message