Mailing-List: contact archiva-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-users@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of wsmoak@gmail.com designates
 209.85.132.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tPOyD7T6fbZXVulOLtrG/eAxeyHigMvze+kgxuMA5gs7ON1Lu7SyX1+t0PiBvaUHM9YAWxhY2O5V+IsAClP7o5gFFP453bGVbNiSs4zAj+q3qpizXfKgM1MpnY9LrKBtb0ReheD1s9PtBNFgihAeYdCkc1lXnAjU96lHG7x3Oa8=
Message-ID: <adba96190711290525q5e302ed8o9ec47a74b2316f81@mail.gmail.com>
Date: Thu, 29 Nov 2007 06:25:40 -0700
From: "Wendy Smoak" <wsmoak@gmail.com>
To: archiva-users@maven.apache.org
Subject: Re: Repository scanning problem in 1.0?
In-Reply-To: <14025501.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <14025501.post@talk.nabble.com>

On Nov 29, 2007 6:07 AM, ArneD <public@degenring.de> wrote:

> After starting up a fresh instance with default configuration, I copied
> parts of my existing repository to Archiva's default internal repository.
> Then I used the "Scan Repository Now" button on the repository
> administration page. Afterwards, all artifacts were visible on the "Browse"
> page. So far so good.
>
> I then copied some more groups of my existing repo to Archiva's default
> internal repository, and used "Scan Repository Now" once again. But this
> time, the "Browse" page did not show the newly added groups. This was quite
> surprising, as the log output of RepositoryScanner clearly showed that
> Archiva DID walk over these new artifacts, without errors or warnings. I
> tried to use the "Update Database Now" button, but still no effect.
>
> I finally touched one of the POM files in the missing groups, i.e. I gave
> the POM file a new timestamp. After doing "Scan Repository Now" again, the
> artifact appeared on the Browse page. When browsing into the artifact,
> however, I get the error message "Unable to find project model for [...]".

I've seen "Unable to find project model for [...]" in recent versions
of Archiva, also using with existing repository contents, but have not
been able to isolate it with publicly available repo data.

Can you come up with steps to reproduce this, and attach zipped
repository contents to a JIRA issue?  It shouldn't take more than a
few artifacts to provoke the problem, once you know the cause.
http://jira.codehaus.org/browse/MRM

Thanks,
-- 
Wendy