The Apache Jenkins build system has built Camel.trunk.notest (build #1983)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1983/
to view the results.
The Apache Jenkins build system has built Camel.2.12.x.notest (build #13)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/13/
to view the results.
Now we have 6 binding +1 votes ningjiang, davsclaus, janstey, cmueller,
bvahdat, cschneider
and 1 no-binding +1 vote: ceposta.
Thanks for your votes, I'm heading to release this staging kit now.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com
Hi Christian,
It's due to xerces in lib/endorsed (required to fix an issue with IBM jdk), and
a forget of the systemPackages property.
I already created the jira and I will fix that for Karaf 2.3.3.
The workaround is to remove xerces jar from lib/endorsed.
Regards
JB
--
Jean-Baptiste Onofré
jb
> We also have camel-velocity, to be complete here.
> What's your issue?
> We took the name from the framework/library we use under the cover.
> Renaming it would be a breaking change. So, I'm -1 for this change.
>
>
> > I feel that the two template components are not properly named...
> >
> > We
Please us the user mailing list for further questions like this as we say
here [1].
Yes, we have a camel-mail component [2] [3].
Valid uri schemas for this component are imap, imaps, nntp, pop3, pop3s,
smtp and smtps [4]. You are right, it's misleading to use "mail://..." at
[2]. I will go and fix
This isn't right.
The name of the JClouds integration component in Camel is camel-jclouds
[1]. The name of this Karaf feature is also camel-jclouds [2].
The servicemix-camel (and also activemq-camel) components are provided by
the ServiceMix (and ActiceMQ) project. This is the reason why they have
We also have camel-velocity, to be complete here.
What's your issue?
We took the name from the framework/library we use under the cover.
Renaming it would be a breaking change. So, I'm -1 for this change.
Best,
Christian
Am 08.09.2013 08:33 schrieb "gliesian" :
> I feel that the two template comp
The camel-spring-redis is because this component is based on spring-data-redis.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitte
Hi
In the coming up Apache Camel 2.12.0, we have the camel-facebook component.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twi
+1
I tested some tutorial examples in Apache Karaf 2.3.2 and Apache Karaf
2.3.1.
I had one problem though. When testing the example
https://github.com/cschneider/Karaf-Tutorial/tree/master/camel/order I
got the error below.
I also tested on camel 2.11.1 and got the same error. So this is no n
11 matches
Mail list logo