Yes, actually we need to report those through the UI. In addition, such an exception should not halt the scan.
Would you mind reporting those in JIRA? - Brett 2008/8/8 Dan Tran <[EMAIL PROTECTED]>: > It turns out the repo scanning encountered and error, and stopped. > > <snip> > 2008-08-07 09:00:05,975 [pool-2-thread-1] ERROR > org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure > - Consumer [repository-purge] had an error when processing file > [/var/maven/repositories/releases/internal/com/fortinet/fortinet/5/5.rip/fortinet-5.pom]: > Invalid path to Artifact: filename format is invalid, should start > with artifactId as stated in path. > org.apache.maven.archiva.consumers.ConsumerException: Invalid path to > Artifact: filename format is invalid, should start with artifactId as > stated in path. > > </snip> > > I really dont know why 5.rip get into my repo, but removing it allows > repo scan to regen my files. > > Now I need to check the log once a while :-) > > -D > > > On Thu, Aug 7, 2008 at 12:55 PM, Dan Tran <[EMAIL PROTECTED]> wrote: >> I removed a version directory ( 3.1-000 ), and remove all metadata >> files of the artifact, and run the scan. The metadata is not regen >> >> /var/maven/repositories/releases/internal/com/fortinet/fortidb/fdb-applboot >> [EMAIL PROTECTED] fdb-applboot]$ ls -al >> total 24 >> drwx------ 3 archiva archiva 4096 Aug 7 11:33 . >> drwx------ 36 archiva archiva 4096 Aug 1 19:26 .. >> drwx------ 2 archiva archiva 4096 Jul 17 10:00 3.0.0 >> >> am I missing something? >> >> BTW, I am using the staging archiva 1.1.1 >> >> -D >> >> On Thu, Aug 7, 2008 at 9:27 AM, Brett Porter <[EMAIL PROTECTED]> wrote: >>> Archiva can regenerate the checksums and the artifact level metadata - >>> that is, a list of versions (it can't regenerate snapshot metadata at >>> this point). >>> >>> This is done by the metadata update consumer and running a scan. You >>> might want to make a copy of the current files before deleting the >>> metadata though. >>> >>> - Brett >>> >>> 2008/8/8 Dan Tran <[EMAIL PROTECTED]>: >>>> Hi I accidentally promoted a set of test released artifacts to my >>>> internal release repository which managed by Archiva. >>>> >>>> I can manually remove the unintended artifacts, how about metadata >>>> file? it is a lots of work to edit the file and regen checksum file >>>> manually while >>>> the box is heavily used. Can archiva help regen the checksum? or >>>> better with self clean the metadata files >>>> >>>> Thanks >>>> >>>> >>>> -D >>>> >>> >>> >>> >>> -- >>> Brett Porter >>> Blog: http://blogs.exist.com/bporter/ >>> >> > -- Brett Porter Blog: http://blogs.exist.com/bporter/
