The Apache Jenkins build system has built Camel.trunk.notest (build #1766)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1766/
to view the results.
On Fri, Jan 18, 2013 at 6:33 PM, Christian Müller
wrote:
> 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.
>
I dont think we nee
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" :
> Hi,
>
> I
On Fri, Jan 18, 2013 at 12:46 PM, Achim Nierbeck
wrote:
> Hi Clause,
>
> thanks for summing up what we talked of on IRC :)
>
Yeah I guess it was a brief summary. I am just trying to push the envelope,
to make developing / using / deploying integration applications with
the Apache stack easier.
T
Hi
On Fri, Jan 18, 2013 at 2:30 PM, Guillaume Nodet wrote:
> Are you talking about the features deployer ?
> Karaf has it already. You can use osgi:install feature:mvn:xxx or drop the
> features file in the deploy directory, or deploy any bundle which has a
> META-INF/org.apache.karaf.shell.fe
Fwiw, when you use the url handler or drop the file in the deploy folder,
both methods just generate a bundle which has the feature file inside
META-INF/org.apache.karaf.shell.features
On Fri, Jan 18, 2013 at 2:53 PM, Achim Nierbeck wrote:
> Oh well,
>
> didn't remember the last possibility of t
Oh well,
didn't remember the last possibility of the features-deployer :)
thanks, Achim
2013/1/18 Guillaume Nodet
> Are you talking about the features deployer ?
> Karaf has it already. You can use osgi:install feature:mvn:xxx or drop the
> features file in the deploy directory, or deploy an
Are you talking about the features deployer ?
Karaf has it already. You can use osgi:install feature:mvn:xxx or drop the
features file in the deploy directory, or deploy any bundle which has a
META-INF/org.apache.karaf.shell.features/*.xml file inside.
On Fri, Jan 18, 2013 at 12:46 PM, Achim Nie
Hi Clause,
thanks for summing up what we talked of on IRC :)
I think it could be even easier.
We could add a bundle tracker for features.xml files that will install
those with the features service.
For this we don't even need a special syntax of the osgi:install url
(and actually if you want a ur
I have been working to integrate ISO8583 messaging with Camel, and the
approach I have taken is to create a custom DataFormat, to perform message
marshaling/unmarshaling in a Camel route, rather than as a full-on endpoint:
this separates the concerns of transformation and transport, in keeping with
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 a
Hi Claus,
I'm my bad, I should not import the class, and it is useless.
I will commit a quick fix for it shortly.
Thanks for pointing that out.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blo
12 matches
Mail list logo
