Return-Path: 
 <users-return-1852-apmail-archiva-users-archive=archiva.apache.org@archiva.apache.org>
Delivered-To: apmail-archiva-users-archive@www.apache.org
Received: (qmail 848 invoked from network); 6 Sep 2008 01:20:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Sep 2008 01:20:27 -0000
Received: (qmail 50734 invoked by uid 500); 6 Sep 2008 01:20:25 -0000
Delivered-To: apmail-archiva-users-archive@archiva.apache.org
Received: (qmail 50683 invoked by uid 500); 6 Sep 2008 01:20:25 -0000
Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@archiva.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@archiva.apache.org>
List-Post: <mailto:users@archiva.apache.org>
List-Id: <users.archiva.apache.org>
Reply-To: users@archiva.apache.org
Delivered-To: mailing list users@archiva.apache.org
Received: (qmail 50672 invoked by uid 99); 6 Sep 2008 01:20:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Sep 2008 18:20:25 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of brett.porter@gmail.com
 designates 209.85.142.189 as permitted sender)
Received: from [209.85.142.189] (HELO ti-out-0910.google.com) (209.85.142.189)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Sep 2008 01:19:25 +0000
Received: by ti-out-0910.google.com with SMTP id w7so422691tib.13
        for <users@archiva.apache.org>; Fri, 05 Sep 2008 18:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type:references;
        bh=byyrFGku5sRmbGSHEdAv8qn+QNFZSPkthT9Q0ODAM9k=;
        b=U2zzJc0wq4xX1SgoKDBJT8O8AgNoZ0sn6kxTu9hxrYiIULb8F8yH0M0vC6Z4UUlrNj
         HOESPppD5+Pjk5wfmyTwIrbn88bZy2ccRcEKrk7IylsMAHdT1stzVXJ6B0ZTN9L8Ztow
         hQO3XX7GO7irOMqTaRLIkmQsVv2EN4jQONrgs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=x05GWPCZFRM/DKf0me+6vQTydHHzgzIHNIFOav7/KT082aRe0SuYnC/9JgooSoZU/0
         R/hCkqFtLP1rUVNBrV4s/8BJ+B2ixRLemO6QFBvM5vY+KkVFVIP6HG0ajcS3dmveaiLh
         /JCdEYd+6Lk4qz1cCr4t9FcvZ0Xl5MWJL+/1Y=
Received: by 10.110.95.15 with SMTP id s15mr15835682tib.45.1220663994990;
        Fri, 05 Sep 2008 18:19:54 -0700 (PDT)
Received: by 10.110.86.15 with HTTP; Fri, 5 Sep 2008 18:19:54 -0700 (PDT)
Message-ID: <9e3862d80809051819r75d9b24dm3d01527a3874f626@mail.gmail.com>
Date: Sat, 6 Sep 2008 11:19:54 +1000
From: "Brett Porter" <brett.porter@gmail.com>
To: users@archiva.apache.org
Subject: Re: Archiva not registering artifacts that are in the repository
In-Reply-To: <860e511e0809051442p689f516ct9d726fae9cc670bc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_97267_4019337.1220663994988"
References: <860e511e0809051442p689f516ct9d726fae9cc670bc@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_97267_4019337.1220663994988
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

How is it deployed to the repository - via HTTP, WebDAV, or placed directly
onto the filesystem (eg, scp)?
The only possibilities I can think of:
- timestamp mismatches that cause it not to be scanned
- the repository it is in is configured not to scan snapshots

Cheers,
Brett

2008/9/6 Scott Carter <carterdevlists@gmail.com>

> I am a newbie with Archiva and am having an issue with Archiva not
> recognizing an artifact that is in our snapshot repository.  We have a
> build
> that deploys it's artifact (a war file) to our repository.  I know that the
> artifact has made it to the repository because I can see it using urls such
> as http://<server>/archiva/repository/snapshots/<path>/1.1.0-SNAPSHOT/ and
> download it from there.  But, if I use the browser from the main archiva
> page the latest version does not show up.  The browser url looks like
> http://<server>/archiva/browse/<path>  .  I can see older versions of this
> build, but not the latest versions.  Why would Archiva not register the
> latest version even though it exists in the repository.
>
> This is not an issue of timing because the archive has been scanned several
> times since the artifact has been added.  I also do not see any obvious
> errors in the archiva log files.  Please help.
>
> Thanks - SC
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

------=_Part_97267_4019337.1220663994988--