Hello, The point is just one in relation to OSGi metadata. The components will be consumed, also, by runtimes that don't need OSGi metadata, so why all the components should be with OSGi metadata and packaged as bundles?
I don't see the reason why. At least the OSGi metadata should be generated under camel Karaf project, instead of being part of the core components I see there is a veto about moving to apache Karaf. It was already a mess before to maintain the features and release camel-karaf with Camel 3, in the end there were one contributor (myself) taking care of them, with some sporadic help. I really don't have the capacity in the future. If the situation is this, as Camel PMC we'll need to discuss this and eventually discontinue, deprecating or make the camel-karaf releases optional. Thanks. Il mer 18 gen 2023, 19:27 Matt Pavlovich <mattr...@gmail.com> ha scritto: > I have a similar question on this point-- > > > On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki <l...@code-house.org> > wrote: > > > > 6) I do not see any sign of what is going to happen with OSGi metadata > which is present for Apache Camel 3.x components. Is Camel 4.x going to > retain OSGi metadata? > > How is maintaining OGSI metadata in Camel a concern? > > Thanks, > Matt Pavlovich
