Hi team, in the last few days I've worked to reduce the CI log file to a reduced size which will simplify any troubleshooting analysis when looking for something in the CI build [1]. I want to give you a quick heads up and report that we have now 50% less log traces than before. While doing the clean up I've realized all the debug, traces and print to std out were all leftovers that proliferated when cloning one piece of code to another (for example, copying the configuration of a component). Mind that this has brought to a long term cluttered amount of useless log that makes it difficult to navigate through a big build such as Camel. And, most of the time it was just a copy from other places.
For any future development, I invite you to review the configuration of log, above all for testing, which may be meaningful during development, but it has reduced utility when the development is stable. Don't leave traces/debug and, above all, print to standard output on. Thanks for the attention, Pasquale. [1] https://issues.apache.org/jira/browse/CAMEL-22607
