The Apache Jenkins build system has built Camel.trunk.notest (build #2812)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2812/
to view the results.
GitHub user jlpedrosa opened a pull request:
https://github.com/apache/camel/pull/1076
Component influxdb
This has two commits, one for the component one for the merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jlpedrosa/cam
Github user jlpedrosa closed the pull request at:
https://github.com/apache/camel/pull/1074
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
They would be node-specific reply queues. No selectors necessary. Selectors
are slow. I'm not asking if I should do it. I'm asking the group if they
see any reason why we have to restrict Exclusive reply queues to one per
destination. I'm looking into patching the code, but if anyone sees an
issue
