The Camel community announces the immediate availability of the new
minor release Camel 2.17.0. This release contains a total of 450+
improvements, fixes and new features applied in the past months by the
community on the Camel master branch.
The artifacts are published and ready for you to downlo
This vote passes with the following results:
+1 binding: 6 (Aki Yoshida, Andrea Cosentino, Christian Müller, Claus
Ibsen, Daniel Kulp, Gregor Zurowski)
+1 non-binding: 2 (Antonin Stefanutti, Thomas Diesler)
I will publish the artifacts for Camel 2.17.0 shortly.
Thanks,
Gregor
On Tue, Mar 22,
I managed to get the CI jobs to complete now with setting higher memory.
The snapshots are now deployed and the CI jobs for osgi is triggered
Triggering a new build of Camel.trunk.itest.karaf
Triggering a new build of Camel.trunk.itest.osgi
Finished: SUCCESS
On Sat, Mar 26, 2016 at 12:36 PM, C
On Sat, Mar 26, 2016 at 11:55 AM, Krzysztof Sobkowiak
wrote:
> Hi
>
> Probably it makes sense to write simple itest for each module which only
> install the module (and dependencies)
> into the Karaf container. We would have simple smoke tests for all modules.
>
Yes we already got that in the te
Oh I forgot the CI jobs are here
https://builds.apache.org/view/A-D/view/Camel/
I got the link from Mueller. Beforehand it was hard/impossible to find
Camel from
https://builds.apache.org/
So I was for a longer time not able to see all these jobs, and just
got the CI emails to look at.
But the O
On Sat, Mar 26, 2016 at 12:12 PM, Raul Kripalani wrote:
> Agree with your points.
>
> 1. If you use lambdas on 2.18, you can't backport the code.
>
> 2. I'll spend some time this weekend installing the bundles on Karaf. Karaf
> 4 is OK, or are we sticking with older versions for 2.x?
>
Karaf 2.x
Agree with your points.
1. If you use lambdas on 2.18, you can't backport the code.
2. I'll spend some time this weekend installing the bundles on Karaf. Karaf
4 is OK, or are we sticking with older versions for 2.x?
3. I'll also run our OSGi itests, but it may be worth having Jenkins do all
thi
Hi
Probably it makes sense to write simple itest for each module which only
install the module (and dependencies)
into the Karaf container. We would have simple smoke tests for all modules.
Regards
Krzysztof
On 26.03.2016 11:12, Claus Ibsen wrote:
> I would like to see more OSGi testing on this
Hi
Good to hear that we may drop the extension, nice work.
For camel-core I have thought of build the manifest.mf by hand so we
can better control it. It seems the bundle plugin has its issues with
different versions to build it, as you say.
Have you tried testing any of these JARs in OSGi? It
