Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Fri, 5 Apr 2013 12:10:44 -0700 (PDT)
From: Babak Vahdat <babak.vahdat@swissonline.ch>
To: dev@camel.apache.org
Message-ID: <1365189044824-5730424.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yNmyS+Spu4hSCuOdqAbLOHd+CCoy6s2JNXmgTTMuBA53TQ@mail.gmail.com>
References: 
 <CALvzYd8zgY-pCCyXMAeYoDOBdufrU2EVqBsTN0yzOQiQm0K_RQ@mail.gmail.com>
 <515B13E7.9010001@gmail.com>
 <CAGB5yN=75nJYRskHdOBPER7ssD2zhvfjKB=J8neH+jSH1YkfqA@mail.gmail.com>
 <CALvzYd9+UPhqYV4-BBCjv_eO_XAfwmhkxE831jdT=dcBPTmu3w@mail.gmail.com>
 <1365149745706-5730383.post@n5.nabble.com>
 <CAGB5yN=eBH6Knb=yt5aCm0hEoqx3Enf47yshbmHKoNNt=Un+xQ@mail.gmail.com>
 <002301ce31e6$419f96a0$c4dec3e0$@de>
 <CAGB5yN=7DDgKjeBZ613D6ij5WHhwkA-e+DG+mLeor5sb3vzN5A@mail.gmail.com>
 <CAGB5yNkAYSaV4+VEgGb6Hw-5JvB1uaRNsxcTmCD21eaVMpsMbg@mail.gmail.com>
 <CAGB5yNmyS+Spu4hSCuOdqAbLOHd+CCoy6s2JNXmgTTMuBA53TQ@mail.gmail.com>
Subject: Re: [DISCUSS] - Moving towards Camel 2.11 release
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi

I've already fixed the failed camel-aws test on Windows as now the
InputStream gets closed properly in case the DeleteAfterWrite option is
enabled by the S3Producer.

Babak


Claus Ibsen-2 wrote
> Hi
>=20
> Okay so we have 2 issues
>=20
> - a test in camel-aws fails on Windows.
> - camel:run in blueprint does not work
>=20
> I will work on the latter tomorrow morning.
> And then look at the failing test on Windows (it indicate a problem
> with not closing a file input stream, causing the file to be locked).
>=20
> IMHO we should have these 2 fixed before we can cut the RC.
>=20
>=20
>=20
>=20
> On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen &lt;

> claus.ibsen@

> &gt; wrote:
>> Hi
>>
>> I am running a full test on Windows.
>>
>> There is a single test in camel-aws that fails. I guess its related to
>> not being able to delete the file.
>> Will dig into this later when getting a bit of time. Either later
>> today or tomorrow morning.
>>
>> If anyone on Windows, then feel free to look into that failing test so
>> we can have it fixed before cutting the 2.11 release.
>>
>>
>> On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen &lt;

> claus.ibsen@

> &gt; wrote:
>>> Just a note to us that we should remember checkin the maven archetype
>>> for the blueprint.
>>> There may be a problem with 2x blueprint on the classpath when using
>>> camel:run
>>>
>>> On Fri, Apr 5, 2013 at 12:13 PM, Jan Mat=C3=A8rne (jhm) &lt;

> apache@

> &gt; wrote:
>>>>> There is a new Apache SMX bundle in VOTE just now.
>>>>> Wonder if we should wait for this release so the Camel bundles can us=
e
>>>>> these upgrades?
>>>>> Or maybe we want to get the 2.11 out sooner?
>>>>
>>>> I think there always will be a coming release and you should not try t=
o
>>>> catch all of them.
>>>> You could upgrade with a 2.12 if necessary.
>>>>
>>>> Just my 2ct
>>>> Jan
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email:=20

> cibsen@

>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email:=20

> cibsen@

>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>=20
>=20
>=20
> --=20
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email:=20

> cibsen@

> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen


--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Mov=
ing-towards-Camel-2-11-release-tp5725088p5730424.html
Sent from the Camel Development mailing list archive at Nabble.com.