Hi And the source code java package names needs to be migrated as well org.apache.camel.karaf -> org.apache.karaf.camel
And documentation is moved over to Apache Karaf, where the karaf camel releases its own new set of documentation/website. The existing Camel Karaf 3.x will be maintained as-is until its EOL. On Wed, Jan 18, 2023 at 12:14 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > This SHOULD also mean that the project should be known as karaf-camel > AND that the artifacts released for download and maven central should have > changed GAVs > > groupId = org.apache.karaf.camel > artifactId = karaf-camel-xxx > version = x.y.z > > For version then it may want to follow the Camel version, eg 4.0.0 > > > > > > > On Wed, Jan 18, 2023 at 11:03 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> 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 >> > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2