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 B0332D3A3 for ; Fri, 19 Oct 2012 20:05:03 +0000 (UTC) Received: (qmail 17715 invoked by uid 500); 19 Oct 2012 20:05:03 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 17620 invoked by uid 500); 19 Oct 2012 20:05:03 -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 17613 invoked by uid 99); 19 Oct 2012 20:05:03 -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 20:05:03 +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.210.50 is neither permitted nor denied by domain of brianf@infinity.nu) Received: from [209.85.210.50] (HELO mail-da0-f50.google.com) (209.85.210.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 20:04:56 +0000 Received: by mail-da0-f50.google.com with SMTP id z20so433847dae.23 for ; Fri, 19 Oct 2012 13:04:34 -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=FVmqJaLSdppylB5g/fBc6Du0wRf8hZxfJhfYn7zN6Ak=; b=p4IBW/tJxcuXnpnWX4bj1gpjXe+E5ML+9UrJXRgPWaPqR/+peAm08VmMC4o15hxHdJ 1KUZ8MphpQxhNcApSSzJhqyqZ5G2JvInEx2GOETH682RP37baSyUl4zJoqmIOtlnPZb0 nk2krMUhDEr4675EWIHA4RIXZuYeQJ7SqsjjKUOgr5LvaVRjzkTDF+FWFMUo/FXWVc6S 6AwVOfdP1tn563U2biyqiPRnePacEQdnJvZA/t2QJmjt2aQZy+58XkXOgauJb7hdyPdq m79xtoeY7VzU/4u/Fy6Z/qQ0rmfUajn5SFqk15bsG96vA+l2lYx4GbqiVZu8Bjf1LrQU EXjg== Received: by 10.68.217.67 with SMTP id ow3mr9312139pbc.26.1350677074483; Fri, 19 Oct 2012 13:04:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.51.168 with HTTP; Fri, 19 Oct 2012 13:04:14 -0700 (PDT) In-Reply-To: <5081ACA7.300@oliver-heger.de> References: <50673D1C.2040508@oliver-heger.de> <507DB6EF.6060500@oliver-heger.de> <5081ACA7.300@oliver-heger.de> From: Brian Fox Date: Fri, 19 Oct 2012 16:04:14 -0400 Message-ID: Subject: Re: Incomplete maven-metadata.xml for commons-configuration To: repository@apache.org Content-Type: multipart/alternative; boundary=e89a8ff246e13b19a904cc6f0358 X-Gm-Message-State: ALoCoQkqRfQch74s+AXQCPI1zvd6ljVLUeGzLRwK2jw2U1CPHi8ZuUCEKhoy/dRJaNoN1rzHPb+5 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff246e13b19a904cc6f0358 Content-Type: text/plain; charset=ISO-8859-1 oooh. that would explain it. They were put through some conversion process on Central to M2ify them, but not on people which was the source for the import to RAO. Mystery solved. On Fri, Oct 19, 2012 at 3:40 PM, Oliver Heger wrote: > Thank you very much Brian! > > I have no clue what could have caused this problem. Maybe it is related to > the fact that older releases were done with Maven 1? > > Regards > Oliver > > Am 19.10.2012 14:50, schrieb Brian Fox: > >> 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 >> > commons-configuration/maven-**metadata.xml >> > >> >> >> >> > --e89a8ff246e13b19a904cc6f0358 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable oooh. that would explain it. They were put through some conversion process = on Central to M2ify them, but not on people which was the source for the im= port to RAO. Mystery solved.

On Fri, Oct = 19, 2012 at 3:40 PM, Oliver Heger <oliver.heger@oliver-heger.de= > wrote:
Thank you very much Brian!

I have no clue what could have caused this problem. Maybe it is related to = the fact that older releases were done with Maven 1?

Regards
Oliver

Am 19.10.2012 14:50, schrieb Brian Fox:
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<= br> 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/reposit= ories/releases/content/commons-configuration/commons-c= onfiguration/maven-metadata.xml

On Tue, Oct 16, 2012 at 3:35 PM, Oliver Heger
<olive= r.heger@oliver-heger.de <mailto:oliver.heger@oliver-heger.de>&g= t; wrote:

=A0 =A0 Anyone who can help out?

=A0 =A0 Am 29.09.2012 20:25, schrieb Oliver Heger:

=A0 =A0 =A0 =A0 Hi,

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

=A0 =A0 =A0 =A0 How can we update this file so that all available released<= br> =A0 =A0 =A0 =A0 versions are
=A0 =A0 =A0 =A0 visible?

=A0 =A0 =A0 =A0 TIA
=A0 =A0 =A0 =A0 Oliver

=A0 =A0 =A0 =A0 [1] https://issues.apache.org/__jira/br= owse/CONFIGURATION-509
=A0 =A0 =A0 =A0 <https://issues.apache.org/jira/browse= /CONFIGURATION-509>
=A0 =A0 =A0 =A0 [2]
=A0 =A0 =A0 =A0 http= ://repo1.maven.org/maven2/__/commons-configuration/__commons-= configuration/maven-__metadata.xml
=A0 =A0 =A0 =A0 <http:/= /repo1.maven.org/maven2//commons-configuration/commons-config= uration/maven-metadata.xml>





--e89a8ff246e13b19a904cc6f0358--