Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 Thanks JB for the proposal. regards, François On 10/02/2023 09:43, Jean-Baptiste Onofré wrote: Hi guys, According to the vote and discussion on this thread, we don't have a consensus to move camel-karaf into the Karaf community. 1. As we have a decent/large number of users on Karaf runni

Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject

On Fri, Feb 10, 2023 at 9:44 AM Jean-Baptiste Onofré wrote: > Hi guys, > > According to the vote and discussion on this thread, we don't have a > consensus to move camel-karaf into the Karaf community. > > 1. As we have a decent/large number of users on Karaf running Camel routes. > 2. As the Cam

Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject

Hi, Sounds like a good plan +1 Regards, Nicolas From: Jean-Baptiste Onofré Sent: Friday, February 10, 2023 09:43 To: dev ; dev Subject: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject Hi guys, According to the vote and discussion on this

[CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject

Hi guys, According to the vote and discussion on this thread, we don't have a consensus to move camel-karaf into the Karaf community. 1. As we have a decent/large number of users on Karaf running Camel routes. 2. As the Camel "core" community doesn't want to maintain OSGi related stuff in camel-c

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Hi, I think it's important to split the discussion into two major aspects: technical aspect and community aspect. - Technically speaking, I don't see camel-karaf very different from camel-spring-boot or camel-quarkus or camel-k. It contains Camel specific to a platform, exactly like camel-quarkus

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

As a side note, it's not only aligning the features, it's also upgrading the servicemix bundles to be able to align, JB knows what I'm talking about. I helped there a lot too (less in the last year or so) and it's really a mess. Il mer 18 gen 2023, 20:43 Romain Manni-Bucau ha scritto: > Le mer.

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Le mer. 18 janv. 2023 à 20:17, Andrea Cosentino a écrit : > Il mer 18 gen 2023, 20:06 Romain Manni-Bucau ha > scritto: > > > Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a > > écrit : > > > > > Hello, > > > > > > The point is just one in relation to OSGi metadata. The components will > > be

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Il mer 18 gen 2023, 20:06 Romain Manni-Bucau ha scritto: > Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a > écrit : > > > 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 >

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

> On Jan 18, 2023, at 12:43 PM, Andrea Cosentino wrote: > > 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? Hi A

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a écrit : > 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'm m

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

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 u

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

I have a similar question on this point-- > On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki 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

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

-1 from my side Given the scope of work and possible improvements I do not see a strong reason to move camel-karaf into karaf-camel hence my veto on the proposal. This vote opens up a dangerous path where Karaf gains more fat and moves into direction of integration product on its own while, til

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 (binding as Karaf PMC member) Freeman On Wed, Jan 18, 2023 at 5:03 AM Jean-Baptiste Onofré 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/R

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 (binding) regards, François On 18/01/2023 11:03, Jean-Baptiste Onofré 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-cor

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 (binding) On Wed, Jan 18, 2023 at 11:03 AM Jean-Baptiste Onofré 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

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 (binding) Le mer. 18 janv. 2023 à 11:03, Jean-Baptiste Onofré a écrit : > 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 (cam

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

+1 (binding) -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, January 18, 2023 at 11:03:27 AM GMT+1, Jean-Baptiste Onofré wrote:

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Any hope to evaluate the "bunch" of users which would move to this new project and not spring-boot/quarkus/anything-hype-cause-$$? Can be great to see if the community wants to focus on karaf or aggregation on the long run due to available/active resources. If we have proofs there is a need and c

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Correct, I mentioned this in my previous email (camel-karaf to karaf-camel). Regards JB On Wed, Jan 18, 2023 at 1:26 PM Claus Ibsen wrote: > > 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 mo

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

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

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

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,

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Hi, Great news! +1 (non-binding) Regards, Nicolas From: Jean-Baptiste Onofr? Sent: Wednesday, January 18, 2023 11:03 To: dev Cc: dev Subject: [VOTE] Accept karaf-camel as new Apache Karaf subproject Hi guys, The Apache Camel community proposed to move Camel

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

Hi Andrea, yes, thanks. I forgot to mention that the move if for Camel 4.x (not the existing branch/version). Regards JB On Wed, Jan 18, 2023 at 11:05 AM Andrea Cosentino wrote: > > As as side note to what JB just wrote: > > as Apache Camel community we'll still maintain the 3.x side of the > p

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

As as side note to what JB just wrote: as Apache Camel community we'll still maintain the 3.x side of the projects, for continuity, Karaf-camel will be the house for the Camel 4.x OSGi support. Thanks. Il giorno mer 18 gen 2023 alle ore 11:03 Jean-Baptiste Onofré < j...@nanthrax.net> ha scritto:

[VOTE] Accept karaf-camel as new Apache Karaf subproject

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, ..