camel-example-cxf-blueprint 2.11-SNAPSHOT is now working on my Karaf 2.3.1
installation after adding the feature camel-blueprint.

Best,
Christian


On Fri, Apr 5, 2013 at 9:10 PM, Babak Vahdat <babak.vah...@swissonline.ch>wrote:

> 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
> >
> > Okay so we have 2 issues
> >
> > - a test in camel-aws fails on Windows.
> > - camel:run in blueprint does not work
> >
> > 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).
> >
> > IMHO we should have these 2 fixed before we can cut the RC.
> >
> >
> >
> >
> > 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èrne (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
> use
> >>>>> 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
> to
> >>>> 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:
>
> > 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:
>
> > 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:
>
> > 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-Moving-towards-Camel-2-11-release-tp5725088p5730424.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

Reply via email to