commit | b7a6b9ba8acb9d8ba438865ea52a936ec71031f5 | [log] [tgz] |
---|---|---|
author | Aurélien Pupier <apupier@redhat.com> | Fri Mar 18 14:33:59 2022 +0100 |
committer | GitHub <noreply@github.com> | Fri Mar 18 14:33:59 2022 +0100 |
tree | 8fba24cb4fbd0671014386ad67aec843fb0deacb | |
parent | 875c3dc7263e78e981f15460d02a87594cc39020 [diff] |
CAMEL-17821 - Provide camel-debug in a profile (#84) * CAMEL-17821 - Provide camel-debug in a profile Currently, Camel textual debugging requires having camel-debug in dependencies. This is an extra dependency that we do not want at runtime. Previously: * main java example is configured having it at runtime. * main xml and yaml doesn't have it I think a possible good practice is to add the dependency in a profile, for instance named `camel.debug` which can be activated with the property camel.debug set to true. This would be nice to be done for all examples but maybe best to start with the 3 more simple/important main (java), main-xml and main-yaml to help starting discussion and see the feedback on it. I think this is even more important for 3.16 as JMX is exposed by default when the dependency is available. Signed-off-by: Aurélien Pupier <apupier@redhat.com> * CAMEL-17821 - Provide note in readmes of compatible examples for camel.debug profile Signed-off-by: Aurélien Pupier <apupier@redhat.com> * CAMEL-17821 - add description in readme to use camel.debug property to activate profile Signed-off-by: Aurélien Pupier <apupier@redhat.com>
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful bean integration.
This project provides examples for Apache Camel.