archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heck, Joe" <>
Subject RE: Artifacts not being indexed
Date Fri, 15 Feb 2008 18:55:43 GMT
I've run into the same issue, but I don't normally push in files through
the file system directly.

In the logging, I saw that the system was finding the file, but it
wasn't making it through it's "steps" to getting pushed into the index.

I never found a real way around this issue, and just instantiated a
whole new archiva setup with the data in there before I fired everything
up to resolve the issue for myself.

I know that doesn't help Carlton's issue, but I thought I'd mention it.


Joseph Heck
Walt Disney Internet Group

-----Original Message-----
.org] On Behalf Of Brown, Carlton
Sent: Friday, February 15, 2008 10:31 AM
Subject: RE: Artifacts not being indexed

> -----Original Message-----
> From: Wendy Smoak []
> Sent: Friday, February 15, 2008 1:17 PM
> To:
> Subject: Re: Artifacts not being indexed
> On Fri, Feb 15, 2008 at 11:06 AM, Brown, Carlton
> <> wrote:
> >  I've got a problem where an artifact downloaded to the filesystem
> cannot
> >  be browsed.  There's some problem with either the database scanning
> >  repository indexing.   The maven metadata files are not being
> generated.
> >  The pom file appears to be good.
> By downloaded, do you mean you are using Archiva as a proxy?  Or do
> you have an external process that is writing to the filesystem?

External process writing to the filesystem.

> The first thing I'd track down is why there is no metadata file.
> There is a checkbox in the Archiva config that will make it create
> missing metadata files.  Try checking that box and then clicking
> 'scan' and then 'update database'.  Does it now show up in browse?

It does not.  That checkbox appears to be enabled by default, and I have
been doing 'scan' and 'update database', so no luck there.  Strangely,
when this happens, the artifacts show up in a search, but you can't
browse to them.  I mean they don't show up under the /archiva/browse
URL, you can use the /repository URL and see them there just fine.
> (I've seen it create missing metadata files.  I'm less sure about its
> ability to repair broken ones.)

It does create missing metadata files, but the process seems to be very
hit-or-miss, and shows almost nothing in the way of useful feedback or

Is there some other, more decisive manual way to force it to re-scan the
entire filesystem and recreate the metadata files?

This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the 
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on 
the contents of this message is prohibited. In such
case please notify us and destroy and delete all 
copies of this transmission.  Thank you.

View raw message