Return-Path: X-Original-To: apmail-repository-archive@www.apache.org Delivered-To: apmail-repository-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D8726D7B3 for ; Fri, 19 Oct 2012 12:51:03 +0000 (UTC) Received: (qmail 39802 invoked by uid 500); 19 Oct 2012 12:51:02 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 39495 invoked by uid 500); 19 Oct 2012 12:50:55 -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 39442 invoked by uid 99); 19 Oct 2012 12:50:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 12:50:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 209.85.220.50 is neither permitted nor denied by domain of brianf@infinity.nu) Received: from [209.85.220.50] (HELO mail-pa0-f50.google.com) (209.85.220.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 12:50:45 +0000 Received: by mail-pa0-f50.google.com with SMTP id hz11so395121pad.23 for ; Fri, 19 Oct 2012 05:50:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=V73zCEfrPurEwwwpFay6YYtutjqviHRyyFmQMM1e3LY=; b=UU/O+4lMUUL+SFsF+pofJwIbT3OJD/7CK1BwGvhTHPyxY3mwgmukqRiZGo17dljcqz j75Gc9mfITUaX3xcX+HZ8qrpxEpCBtGZW1C1siUW9+MjCJXBKieP5z9QjYEa2nExBFFP /SMEf9qz5k7UkRY6FOMsmpZsdKEOhK8EEuVQeUGAsFLQkIsoaxKUXRxiWv8MntwnbGqU w0hEkV1c76Iolo/EjBwMLD8R6YJu6X48ABiGG3OHC57js6DhmHxUqOaM2EFk9wq43gZ2 UsyZpNlFTS7XTJS7D122qN6iCZknkhxQlxeP8PGpCMQiaJHMkpN2HO/QVy2jxyE2xj+w 1nWg== Received: by 10.68.130.70 with SMTP id oc6mr5375290pbb.104.1350651024134; Fri, 19 Oct 2012 05:50:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.51.168 with HTTP; Fri, 19 Oct 2012 05:50:03 -0700 (PDT) In-Reply-To: <507DB6EF.6060500@oliver-heger.de> References: <50673D1C.2040508@oliver-heger.de> <507DB6EF.6060500@oliver-heger.de> From: Brian Fox Date: Fri, 19 Oct 2012 08:50:03 -0400 Message-ID: Subject: Re: Incomplete maven-metadata.xml for commons-configuration To: repository@apache.org Content-Type: multipart/alternative; boundary=047d7b10cf3782516c04cc68f20d X-Gm-Message-State: ALoCoQlZ6umRhioCQv+WcAUYx1RJw0CNLs0M+Z92yGd6g6agV3oy4jb3xmd3+cxeOsoxlfNZrYUf X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10cf3782516c04cc68f20d Content-Type: text/plain; charset=ISO-8859-1 Weird, it seems like prior to the move from people to Nexus, someone deleted all the old releases because I went back and checked the archive folder and it had only 1.7 and 1.8, which were moved to Nexus. I restored the old versions* back to Nexus by pulling them from Central and Nexus has rebuilt the metadata[1]. It will be picked up on Central on the next sync today. * I didn't pull over the versions labeled 200* since they would appear in the Metadata sort as the most recent release. They are still on Central, but not in Nexus so that the metadata is generated properly. [1] https://repository.apache.org/service/local/repositories/releases/content/commons-configuration/commons-configuration/maven-metadata.xml On Tue, Oct 16, 2012 at 3:35 PM, Oliver Heger wrote: > Anyone who can help out? > > Am 29.09.2012 20:25, schrieb Oliver Heger: > > Hi, >> >> on Apache Commons Configuration we have a bug report [1] that the >> maven-metadata.xml file for this project does not list all of the >> available versions. Actually only the versions 1.7, 1.8, and the most >> recent 1.9 are listed; older versions are dropped. >> >> How can we update this file so that all available released versions are >> visible? >> >> TIA >> Oliver >> >> [1] https://issues.apache.org/**jira/browse/CONFIGURATION-509 >> [2] >> http://repo1.maven.org/maven2/**/commons-configuration/** >> commons-configuration/maven-**metadata.xml >> >> > --047d7b10cf3782516c04cc68f20d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Weird, it seems like prior to the move from people to Nexus, someone d= eleted all the old releases because I went back and checked the archive fol= der and it had only 1.7 and 1.8, which were moved to Nexus. I restored the = old versions* back to Nexus by pulling them from Central and Nexus has rebu= ilt the metadata[1]. It will be picked up on Central on the next sync today= .
=A0
=A0
* I didn't pull over the versions labe= led 200* since they would appear in the Metadata sort as the most recent re= lease. They are still on Central, but not in Nexus so that the metadata is = generated properly.
On Tue, Oct 16, 2012 at 3:35 PM, Olive= r Heger <oliver.heger@oliver-heger.de> wrote:
=
Anyone who can help out?

Am 29.09.2012 20:25, schrieb Oliver Heger:

Hi,

on Apache Commons Configuration we have a bug report [1] that the
maven-metadata.xml file for this project does not list all of the
available versions. Actually only the versions 1.7, 1.8, and the most
recent 1.9 are listed; older versions are dropped.

How can we update this file so that all available released versions are
visible?

TIA
Oliver

[1] https://issues.apache.org/jira/browse/CONFIGURATION-5= 09
[2]
http://repo1.maven.org/mav= en2//commons-configuration/commons-configuration/maven-metadata.xml



--047d7b10cf3782516c04cc68f20d--