[DISCUSS] Moving smooks-camel-catridge to Apache Camel

[Claude]

Hello,

Claus from the Apache Camel project has proposed to move back the Camel cartridge codebase to the Camel repo so that it can be included out-of-the-box in Camel. 

I'm generally in favour for the reasons he gave in the issue. Besides, the cartridge was already distributed with Camel a long time ago before it was dropped (I believe due to license issues but now it isn't a problem because the Smooks codebase is licensed under Apache-2.0 as well). However, I'm recommending that the cartridge is forked instead of moved to see how things pan out. My primary concern is that this might impact the release cadence of any repos (e.g., smooks-examples) that depend on the cartridge. Long-term, if we don't hit any major issues, we can retire the cartridge repo.

Thoughts?

Claude

[Tom Fennelly]

Makes sense imo.

--
You received this message because you are subscribed to the Google Groups "Smooks Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smooks-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/smooks-dev/87856f82-9361-47e5-b4c7-0674de20e9f0n%40googlegroups.com.

[Claude]

I'm realising that probably we can't deprecate the whole cartridge because the cartridge allows the developer to send data to Camel endpoints from within Smooks as well. In other words, some cartridge functionality can be deprecated and eventually stripped away, but not all of it.

Claude