Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.220.177 as permitted sender)
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
         :content-type:content-transfer-encoding;
        b=q1umph9Gs5Le+0sTbMC2ZYyKC2wBHIS0rfxdxCymv4WvfK5YFgAKmkz2cbEnzfHUfu
         YbhYgpfVHv+2kffAbvjF+pFjj5cSjlXALhbRljl5kZbatoEm9ZjGTvwdtY1Xe2t8hTj6
         +v8FDiL0RVmX4x219QGbV3MuPduBNw7oCrNVw=
MIME-Version: 1.0
In-Reply-To: <2748945d0904200513n2e25da23s7ce408c5d98c469d@mail.gmail.com>
References: <5380c69c0904190103q37ed510em6c199d0bc70a45dc@mail.gmail.com>
	<2748945d0904200513n2e25da23s7ce408c5d98c469d@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Mon, 20 Apr 2009 14:19:51 +0200
Message-ID: <5380c69c0904200519jdb29446wfdd1a6ac7acf491d@mail.gmail.com>
Subject: Re: Camel on Hudson - why is camel-jetty not run?
To: dev@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Apr 20, 2009 at 2:13 PM, Jon Anstey <janstey@gmail.com> wrote:
> camel-jetty looks to be running it the last completed build
> http://hudson.zones.apache.org/hudson/job/Camel/114/org.apache.camel$camel-jetty/console
>
> What build are you looking at? I think the current one is still building so
> the results are not complete.
Well I guess Hudson and Nexus spooked me this weekend. I was on Nexus
1.2.1 and upgraded to 1.3.3 and then suddenly camel-jetty started
failing. It worked before :)
And the failure in camel-jetty I did not see in the hudson build
reports over the weekend.

Well anyway its there. Just wondered if it was disabled for some reason.


>
> On Sun, Apr 19, 2009 at 5:33 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>
>> Hi
>>
>> Looking at:
>> http://hudson.zones.apache.org/hudson/job/Camel/lastBuild/testReport/
>>
>> The camel-jetty component is not tested. Is there a reason for this?
>>
>> And the new camel-itest-osgi fails constantly.
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>> Apache Camel Reference Card:
>> http://refcardz.dzone.com/refcardz/enterprise-integration
>>
>
>
>
> --
> Cheers,
> Jon
>
> http://janstey.blogspot.com/
>


-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration