The Apache Jenkins build system has built Camel.trunk.notest (build #2477)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2477/
to view the results.
The Apache Jenkins build system has built Camel.2.15.x.notest (build #117)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.15.x.notest/117/
to view the results.
hello all i am new to camel
I have few questions how can we stop certain routes instead of completely
stopping the whole camel context and also is there any other alternative for
Thread.sleep(); method for processing.TIA
--
View this message in context:
http://camel.465427.n5.nabble.com/New-t
Pushed to master but not to camel-2.14.x because the feature resolves
correctly in that version. It turns out the problem came with an SMX Specs
version upgrade 2.2.0 => 2.4.0.
BTW - SMX Specs 2.5.0 is out so we should upgrade to that on master.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member
Pushed fix for camel-sip. It turns out that the referenced Java SIP specs
bundle was not exporting any packages, hence leading to the resolution
issue.
As far as I'm concerned, you can cut the new RC, Dan.
Raúl.
On Fri, Aug 14, 2015 at 6:44 PM, Raul Kripalani wrote:
> Had a quick look at the f
Had a quick look at the failures, and I was able to fix camel-sip. Pushing
soon.
Was not able to reproduce camel-hazelcast and camel-vertx; must've been a
coexistence issue with another feature.
Please wait until you see my push to cut the new RC.
Regards,
*Raúl Kripalani*
Apache Camel PMC Memb
Canceling to rebuild with the snappy update to fix many of the osgi components.
Dan
> On Aug 13, 2015, at 12:16 PM, Daniel Kulp wrote:
>
> This is a vote to release Apache Camel 2.15.3. It’s been quite a while
> since 2.15.2 and with lots of bugs fixed, it would be great to get it out
> t
> On Aug 14, 2015, at 1:01 PM, Raul Kripalani wrote:
>
> Dan,
>
> Thanks for updating snappy on commit 1234e0a2d.
>
> What's your call? Shall we cancel this release and start a new one? If we
> cancelled attempt #1 due to a freemarker OSGi dep issue, I think this issue
> deserves the same trea
Dan,
Thanks for updating snappy on commit 1234e0a2d.
What's your call? Shall we cancel this release and start a new one? If we
cancelled attempt #1 due to a freemarker OSGi dep issue, I think this issue
deserves the same treatment. Actually, since it affects more components,
all the more reason t
HI devs,
I am trying to write out file using camel-ftp on client's ftp server. But I
found some time camel able to write and sometime it's not.
Same scenarion I tested by writing file on my ftp server, it is working
perfectly. But I want guaranteed write (without fail) on client's ftp
server.
Hi,
I would recommend to troubleshoot this in the following way:
from("restlet:http://localhost:8090/validateCustomer?custName=XXX";).log("response
from webservice is ${body}");
or you can redirect the output to stdout using the stream component.
from("restlet:http://localhost:8090/validateCusto
11 matches
Mail list logo