On Fri, Feb 15, 2008 at 11:31 AM, Brown, Carlton
<[EMAIL PROTECTED]> wrote:
> Is there some other, more decisive manual way to force it to re-scan the
> entire filesystem and recreate the metadata files?
Sure. Stop Archiva, and delete both the Lucene index files and the
Archiva database.
Look
> -Original Message-
> From: Wendy Smoak [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 15, 2008 1:17 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Artifacts not being indexed
>
> On Fri, Feb 15, 2008 at 11:06 AM, Brown, Carlton
> <[EMAIL PROTECTED]> wrote:
>
> > I've got a
Hi,
I've got a problem where an artifact downloaded to the filesystem cannot
be browsed. There's some problem with either the database scanning or
repository indexing. The maven metadata files are not being generated.
The pom file appears to be good.
How can I troubleshoot this problem and det
On Fri, Feb 15, 2008 at 8:57 AM, Brown, Carlton
<[EMAIL PROTECTED]> wrote:
> What component would that be under?
Just leave it as 'unknown' if nothing looks relevant. We can update
it later. Thanks!
--
Wendy
On Fri, Feb 15, 2008 at 4:00 AM, Sunita Pahwa <[EMAIL PROTECTED]> wrote:
> I am using archiva 1.0.1 standalone version.
> When I created new user from 'User Management', On clicking 'create user' it
> gives following exception:
The inability for admin-created users to log in is a known issue in
I am using archiva 1.0.1 standalone version.
When I created new user from 'User Management', On clicking 'create user' it
gives following exception:
008-02-15 16:23:06,251 [SocketListener0-0] WARN
com.opensymphony.xwork.util.Og
lUtil - Caught OgnlException while setting property 'principal' on ty