Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 36953 invoked from network); 1 Apr 2009 19:15:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Apr 2009 19:15:51 -0000 Received: (qmail 12171 invoked by uid 500); 1 Apr 2009 19:15:51 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 12072 invoked by uid 500); 1 Apr 2009 19:15:51 -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 12060 invoked by uid 99); 1 Apr 2009 19:15:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 19:15:50 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brianf@reply.infinity.nu designates 205.210.42.66 as permitted sender) Received: from [205.210.42.66] (HELO mailout.easydns.com) (205.210.42.66) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 19:15:40 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id A14A74821F; Wed, 1 Apr 2009 15:15:04 -0400 (EDT) Received: from mailout.easydns.com ([127.0.0.1]) by localhost (mailout.easydns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIb4XRCCWs99; Wed, 1 Apr 2009 15:15:04 -0400 (EDT) Received: from intrepid.infinity.nu (c-98-229-225-70.hsd1.nh.comcast.net [98.229.225.70]) by mailout.easydns.com (Postfix) with ESMTP id 637FD48413; Wed, 1 Apr 2009 15:15:04 -0400 (EDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: M2 repo error X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 1 Apr 2009 15:07:46 -0400 Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E53C1DF@intrepid.infinity.nu> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: M2 repo error Thread-Index: AcmyXrTrhiM09j0aSE2l4f/Spby4TAAnmC1g References: <200903160915.57895.andy@datanucleus.org> <1a5b6c410903200917j49a9aa88tc905e9ebfe4fbbc6@mail.gmail.com> From: "Brian E. Fox" To: , "Carlos Sanchez" Cc: "Apache JDO project" X-Virus-Checked: Checked by ClamAV on apache.org Shouldn't the jdo artifacts come to central directly from Sun? -----Original Message----- From: Craig.Russell@Sun.COM [mailto:Craig.Russell@Sun.COM]=20 Sent: Tuesday, March 31, 2009 8:13 PM To: Carlos Sanchez Cc: repository@apache.org; Apache JDO project Subject: Re: M2 repo error Hi Carlos, Can you please take a look at people.apache.org/repo/m2-ibiblio-rsync-=20 repository/javax/jdo and verify that these artifacts (maven-=20 metadata.xml, signature, checksum) look correct? If so, please push =20 them to ibiblio. There should be only three versions: 2.0, 2.1, and 2.2. Thanks, Craig On Mar 20, 2009, at 9:17 AM, Carlos Sanchez wrote: > Maybe you haven't got my message: > > It may have been auto generated at some point. > If you use Maven 2 it will be generated. > You can override it by putting a new one under > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ (and > letting me know to setup an automatic sync) > > > On Fri, Mar 20, 2009 at 9:14 AM, Craig L Russell > wrote: >> Any ideas? >> >> Craig >> >> On Mar 16, 2009, at 10:43 AM, Craig L Russell wrote: >> >>> Hi, >>> >>> I don't recall pushing this artifact to the repository; is it >>> auto-generated perhaps? >>> >>> Any help in fixing it would be appreciated. >>> >>> Thanks, >>> >>> Craig >>> >>> still a mvn newbie >>> >>> Begin forwarded message: >>> >>>> From: Andy Jefferson >>>> Date: March 16, 2009 2:15:57 AM PDT >>>> To: jdo-dev@db.apache.org >>>> Subject: M2 repo error >>>> Reply-To: jdo-dev@db.apache.org >>>> >>>> On http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/ >>>> there is a file >>>> >>>> http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/maven-m etadata.xml >>>> which is presumably used by Maven(2) in determining what versions =20 >>>> it is >>>> prepared to let the world know about. There is no 2.2 entry in =20 >>>> it, nor >>>> 2.1 >>>> for that matter. >>>> >>>> Means that whenever anyone specifies to use "apache-jdo" >>>> (javax.jdo/jdo2-api) >>>> between 2.2 and 3.0 they get the really informative >>>> >>>> Couldn't find a version in [SNAPSHOT, 2.0-beta, 2.0-rc1, 2.0, >>>> 2.1-SNAPSHOT] to >>>> match range [2.2,3.0) >>>> javax.jdo:jdo2-api:jar:null >>>> >>>> >>>> Perhaps there's someone who can fix this ? >>>> >>>> Regards >>>> -- >>>> Andy (DataNucleus - http://www.datanucleus.org) >>> >>> Craig L Russell >>> Architect, Sun Java Enterprise System http://db.apache.org/jdo >>> 408 276-5638 mailto:Craig.Russell@sun.com >>> P.S. A good JDO? O, Gasp! >>> >> >> Craig L Russell >> Architect, Sun Java Enterprise System http://db.apache.org/jdo >> 408 276-5638 mailto:Craig.Russell@sun.com >> P.S. A good JDO? O, Gasp! >> >> Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:Craig.Russell@sun.com P.S. A good JDO? O, Gasp!