Hi Claus, Thanks for applying the patch.
Regarding what you already said by this discussion: > However as we just use it for testing, then we can take a short cut > and possible remove the log4j in the pom.xml file. But for the > examples we should not, as it can help show best practice to end > users, that they can setup log4j dependency and control which version > they want to use. IMHO I think even by examples the direct dependencies to log4j is obsolete and should be removed (it gives a wrong feeling to the users, that they should do it in the same way, which to me is NOT the best practice), as I think the camel users can NOT control which version of log4j they want to use IF they instruct camel to use log4j through a direct dependency to slf4j-log4j12. The simple foo.zip example I provided before by this dicussion proves this fact, see http://camel.465427.n5.nabble.com/Camel-freemarker-tp4693216p4695940.html I even think that the camel users should be sensibilized on WIKI or through the README.txt of examples that a version clash of log4j could cause problems. I have already a patch available on my workspace for the examples as well and could reopen the ticket and provide that as well. Any idea? Regards, Babak -- View this message in context: http://camel.465427.n5.nabble.com/Camel-freemarker-tp4693216p4697863.html Sent from the Camel - Users mailing list archive at Nabble.com.
