Hi guys, The Apache Camel community proposed to move Camel Karaf to the Apache Karaf project (as a new subproject).
As a reminder, Camel Karaf provides: - support Camel Contexts/Routes as OSGi services (camel-core-osgi) - Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, ...) - wrapping of Camel components as Karaf features (providing a features repository XML) I think there are a bunch of users using camel-karaf, so, from a community perspective, it would be great to maintain it. Furthermore, I already have some ideas to improve karaf-camel, like avoiding to wrap each Camel component as an OSGi bundle, but instead creating a kind of Uber jar to simplify deployment and have more reliable behavior. Concretely, accepting camel-karaf as Karaf subproject would mean: - maintain the existing code, and improving it, preparing kind of roadmap for camel-karaf - deal with Camel versions and components (and all difficulties that it could cause in an OSGi context :) ) - maintain camel-karaf specific documentation - vote for the releases (the PMC members would be the Karaf ones, so binding vote from Karaf PMC members) I submit accepting camel-karaf (so karaf-camel :)) as new Karaf subproject to your vote: Please vote to approve this release: [ ] +1 Approve camel-karaf as new Karaf subproject [ ] -1 Don't approve camel-karaf as new Karaf subproject (please provide specific comments) This vote will be open for at least 72 hours. Thanks, Regards JB
