Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 74.125.92.149 as permitted sender)
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:content-transfer-encoding:content-disposition
         :references;
        b=v5Fjj/yRpgsKXFDLyj2p4pb4K2q9TrQ3gy48OS+Fqv3mhic3Ex8Gc7T1xsg1j+a4xz
         1QkvQhHBuyOZhRGvAC/aC5nN6JSO8HNdANUbH5BslKcQanUeV2LqYMuA3bda8XK6B3kO
         roUWYxvjHByOidG7XVK89XJ/UyXDxJyaboXtM=
Message-ID: <5380c69c0812290718p3d32ee8aqaafa27e290bb4bdd@mail.gmail.com>
Date: Mon, 29 Dec 2008 16:18:09 +0100
From: "Claus Ibsen" <claus.ibsen@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Re: FW: [nexus-user] Bad metadata in central repo - nexus to the
 rescue ?
In-Reply-To: <7b3355cb0812231458q5ab3eaaesad732dc1d96f0a18@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <224f32340812231139t78e107aene9268c11efcdda1a@mail.gmail.com>
	 <C576B05F.35E9F%brianf@reply.infinity.nu>
	 <7b3355cb0812231458q5ab3eaaesad732dc1d96f0a18@mail.gmail.com>

Hi

Hadrian can you help out here?

What can be done next time we release a new version?
Should we have a new somekind of manual upload/step you should do
according to the release procedures?

Looking at eg ActiveMQ it has a correct metadata file with version
info of each release.


On Tue, Dec 23, 2008 at 11:58 PM, Bruce Snyder <bruce.snyder@gmail.com> wrote:
> It looks like the Maven metadata for Camel is incorrect. Can someone
> correct this?
>
> Bruce
>
> ------ Forwarded Message
> From: Thomas Dudziak <tomdzk@gmail.com>
> Reply-To: <nexus-user@sonatype.org>
> Date: Tue, 23 Dec 2008 11:39:40 -0800
> To: <nexus-user@sonatype.org>
> Subject: [nexus-user] Bad metadata in central repo - nexus to the rescue ?
>
> Hi all,
>
> I yesterday tried to build a project that depends on
> org.apache.camel:camel-core, version 1.4. Our trusty Nexus repository
> dutifully tried to fetch the artifact from the central repos (we have
> both Maven2 and Ibiblio configured), but failed with
>
> [INFO] Failed to resolve artifact.
>
> Couldn't find a version in [1.5.0] to match range [1.4.0,1.4.0]
>  org.apache.camel:camel-core:jar:null
>
> from the specified remote repositories:
>  snapshots (http://public-snapshots),
>  central (http://central)
>
> So I did some spot checking in the repo, and the 1.4 version seems to
> be in the repo:
>
> http://repo2.maven.org/maven2/org/apache/camel/camel-core/1.4.0/
>
> (along with other, older versions).
> However, the metadata file only lists the latest version:
>
> <metadata>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-core</artifactId>
> <version>1.5.0</version>
> <versioning>
> <release>1.5.0</release>
> <versions>
> <version>1.5.0</version>
> </versions>
> <lastUpdated>20081028033115</lastUpdated>
> </versioning>
> </metadata>
>
> Of course this is a really stupid bug in the central repo software,
> but what I'm actually wondering is, whether Nexus could help in cases
> like this ? Since the artifact is obviously there (as a simple HTTP
> GET or perhaps even HEAD can prove), would it be possible for Nexus to
> bypass the metadata file and fetch the artifact directly from its
> designated location ? As far as I'm aware, there are lots of these bad
> metadata files in the central repo, and having to upload them manually
> is really painful.
>
>
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>


-- 

/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/