Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 47698 invoked from network); 26 Aug 2009 11:09:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Aug 2009 11:09:35 -0000 Received: (qmail 97897 invoked by uid 500); 26 Aug 2009 11:09:35 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 97792 invoked by uid 500); 26 Aug 2009 11:09:35 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 97784 invoked by uid 99); 26 Aug 2009 11:09:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2009 11:09:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kldavis4@gmail.com designates 209.85.220.228 as permitted sender) Received: from [209.85.220.228] (HELO mail-fx0-f228.google.com) (209.85.220.228) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2009 11:09:25 +0000 Received: by fxm28 with SMTP id 28so35597fxm.17 for ; Wed, 26 Aug 2009 04:09:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=xBbyr5wvSiPVyFirOGI59iZtPnYI1vU8Lyyak1ye/hA=; b=UaLEQq9bAJAcVEzYOCBgJO/y0GhXJ4bk0NjGoHmHPpNbv/lRbbhSKsSshGmKyraWoO D4BSR5K/OWgFgv7IymGJ1eTodK8HFCDttBmW1CGZHvd6RRsCYFQi6lydKsr2DVRhx4w9 m0XZvVoYwhooFlhg4UNZ9atg1d2v+0zVqBEy0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=RXqF658fhRxjI6jk+UiQNxrBWVplS1fdaSjaZ2EEUj1YXXDh+nX++7W1QNVAKotnHw CjIg4ZI+OumXeqQ0PArFps610DJpld1a/dF4+aLOHeZliNyWW4lk5A7Og2xtdkb0eFhk 6rdSIPD4+tx2IOS7zH4+uB+iV2z3lCDKG7EWs= MIME-Version: 1.0 Received: by 10.239.163.199 with SMTP id q7mr748716hbd.29.1251284945071; Wed, 26 Aug 2009 04:09:05 -0700 (PDT) In-Reply-To: References: From: Kelly Davis Date: Wed, 26 Aug 2009 07:08:45 -0400 Message-ID: Subject: Re: Index for http://repository.apache.org/snapshots/ appears to be invalid To: Brian Fox Cc: repository@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Brian, Thanks for your reply. The issue turned out to be a bad sonatype repo that was missing some artifacts. Once I removed that repository, the problems were resolved. Kelly On Fri, Aug 21, 2009 at 2:10 PM, Brian Fox wrote: > The index may be out dated (i'll have to check why) but this wouldn't > affect you being able to access the file. > > On Fri, Aug 21, 2009 at 10:52 AM, Kelly Davis wrote: >> I have our local Nexus server pointed at the apache snapshots repo and >> I have been having problems with some maven builds beginning on August >> 17, with some plugin artifacts not being found. For example, when I >> run the java doc report it says it can't find >> maven-javadoc-plugin-2.6.1-SNAPSHOT.jar. I can navigate my browser to >> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-javadoc-plugin/2.6.1-SNAPSHOT/ >> and find the artifact, but if in Nexus I search for the artifact, it >> doesn't find it. Browsing the index shows that the only version it >> sees is 2.5.1-SNAPSHOT. I have triedTh re-indexing and it doesn't help. >> I inspected the index file and it doesn't look like it has the >> 2.6.1-SNAPSHOT version in it. I think the problem with the build is >> that it is looking at >> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-javadoc-plugin/maven-metadata.xml >> which indicates that the 2.6.1-SNAPSHOT version is the latest, but >> then our copy of Nexus looks at its index and doesn't find that >> version. Specifying a release version of the maven-javadoc-plugin >> works fine, but I have become accustomed to not specifying the >> version. >> >> Kelly >> >