The Apache Jenkins build system has built Camel.trunk.notest (build #2729)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2729/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/955
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/956
---
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 enabl
GitHub user guillaumeterral opened a pull request:
https://github.com/apache/camel/pull/956
CAMEL-9903 Fix jmx operations when jmx domain is custom + test
I retrieve the jmx domain from the management agent where it has been
customized using JVM property or ManagementAgent bean acco
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/955
CAMEL-9875 CamelBlueprintTestSupport lacks support for multiple PIDs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-98
Hi Thomas,
I guess we should put a message like "do not edit in confluence" when migration
will be finished. For the moment we need to upgrade both side in my opinion.
Same for the links.
In camel-website there are all the .adoc outside of components stuff.
For the moment the plan is to migrat
Hi,
Shouldn't we put some warning on every component's page "do not edit in
confluence"? Or on every page that is already migrated?
Right now I find it hard to get a status on what is already migrated (except
components).
Shouldn't the component pages in confluence link to the new ones?
Some th
Github user arnaud-deprez closed the pull request at:
https://github.com/apache/camel/pull/949
---
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 i
Github user bgaudaen closed the pull request at:
https://github.com/apache/camel/pull/951
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/954
---
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 enabl
GitHub user vickysirwani opened a pull request:
https://github.com/apache/camel/pull/954
Updated DefaultExceptionPolicyStrategy documentation
Fixed typo.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vickysirwani/camel master
A
11 matches
Mail list logo
