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 christian.mueller@gmail.com
 designates 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALhQg-Y9pJNSfV_D3ttVQnN5R=gfeJhSU1LXo+EEaWbs6tH22Q@mail.gmail.com>
References: 
 <CALhQg-Y9pJNSfV_D3ttVQnN5R=gfeJhSU1LXo+EEaWbs6tH22Q@mail.gmail.com>
Date: Fri, 18 Jan 2013 18:33:10 +0100
Message-ID: 
 <CALvzYd9u7RcnDh1pd=AWr_Zp444C-wa04rKbJx6oDVicjEzHfg@mail.gmail.com>
Subject: Re: [camel-extra] Fixed unstable build
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=f46d044787c55a424204d3938159

--f46d044787c55a424204d3938159
Content-Type: text/plain; charset=ISO-8859-1

Have in mind the trunk is already 2.11-SNAPSHOT. You have to create a
camel-extra-2.10.x maintenane branch first and merge your changes from
trunk into this branche. Afterwards you can release camel-extra-2.10.1.

Sent from a mobile device
Am 18.01.2013 11:34 schrieb "Henryk Konsek" <hekonsek@gmail.com>:

> Hi,
>
> I wanted to proceed with the missing camel-extra releases, but I found
> out that zeromq component tests sometimes fails (~20% of runs).
>
> The cause was the ZeromqConsumerTest#stopInterruptsExecutor test. The
> assertions in tests could not be satisfied if executor didn't manage
> to close the jobs after call to the ExecutorService#shutdownNow
> method.
>
> I refactored the test (rev962) to make it more "Mockito-sh" and thread
> safe.
>
> I'll continue with releasing Camel Extra from this point. The one
> thing I want to fix before 2.10.1 release is OSGI Camel imports issue
> [1].
>
> Best regards.
>
> [1]
> http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=30
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>

--f46d044787c55a424204d3938159--