You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2023/02/10 08:43:20 UTC
[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-core.
I propose the following:
1. We keep camel-karaf at Camel (as we have camel-quarkus,
camel-spring-boot, ..., I hope we don't have anything in camel-core
needed/required by camel-quarkus or camel-spring-boot, else it
wouldn't be fair for camel-karaf ;) )
2. Camel Core can remove OSGi related stuff (headers,
maven-bundle-plugin, ...), we will implement a new approach in
camel-karaf (with a custom deployer as I proposed before for
instance).
3. I will do a complete cleanup on the camel-karaf main branch,
already upgrading to camel 4 to prepare camel-karaf 4.
Thoughts ?
Regards
JB
Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject
Posted by fpapon <fp...@apache.org>.
+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 running Camel routes.
> 2. As the Camel "core" community doesn't want to maintain OSGi related
> stuff in camel-core.
>
> I propose the following:
>
> 1. We keep camel-karaf at Camel (as we have camel-quarkus,
> camel-spring-boot, ..., I hope we don't have anything in camel-core
> needed/required by camel-quarkus or camel-spring-boot, else it
> wouldn't be fair for camel-karaf ;) )
> 2. Camel Core can remove OSGi related stuff (headers,
> maven-bundle-plugin, ...), we will implement a new approach in
> camel-karaf (with a custom deployer as I proposed before for
> instance).
> 3. I will do a complete cleanup on the camel-karaf main branch,
> already upgrading to camel 4 to prepare camel-karaf 4.
>
> Thoughts ?
>
> Regards
> JB
--
--
François
Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject
Posted by fpapon <fp...@apache.org>.
+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 running Camel routes.
> 2. As the Camel "core" community doesn't want to maintain OSGi related
> stuff in camel-core.
>
> I propose the following:
>
> 1. We keep camel-karaf at Camel (as we have camel-quarkus,
> camel-spring-boot, ..., I hope we don't have anything in camel-core
> needed/required by camel-quarkus or camel-spring-boot, else it
> wouldn't be fair for camel-karaf ;) )
> 2. Camel Core can remove OSGi related stuff (headers,
> maven-bundle-plugin, ...), we will implement a new approach in
> camel-karaf (with a custom deployer as I proposed before for
> instance).
> 3. I will do a complete cleanup on the camel-karaf main branch,
> already upgrading to camel 4 to prepare camel-karaf 4.
>
> Thoughts ?
>
> Regards
> JB
--
--
François
Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject
Posted by Nicolas Filotto <nf...@talend.com>.
Hi,
Sounds like a good plan +1
Regards,
Nicolas
________________________________
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Friday, February 10, 2023 09:43
To: dev <de...@camel.apache.org>; dev <de...@karaf.apache.org>
Subject: [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-core.
I propose the following:
1. We keep camel-karaf at Camel (as we have camel-quarkus,
camel-spring-boot, ..., I hope we don't have anything in camel-core
needed/required by camel-quarkus or camel-spring-boot, else it
wouldn't be fair for camel-karaf ;) )
2. Camel Core can remove OSGi related stuff (headers,
maven-bundle-plugin, ...), we will implement a new approach in
camel-karaf (with a custom deployer as I proposed before for
instance).
3. I will do a complete cleanup on the camel-karaf main branch,
already upgrading to camel 4 to prepare camel-karaf 4.
Thoughts ?
Regards
JB
As a recipient of an email from the Talend Group, your personal data, including your contact information, will be processed by our systems. For information about the collection and use of your personal information by Talend Group, our privacy and security practices, and your data protection rights, including rights to opt-out of machine learning techniques we use to analyze communications, please see our Privacy Notice. <https://www.talend.com/privacy-policy/>
To manage or discontinue promotional communications, use the communication preferences portal.<https://info.talend.com/emailpreferencesen.html> To exercise your data protection rights, use the privacy request form. <https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704c>
Contact Us <https://www.talend.com/contact/> Co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes, France
Re: [CANCEL] [VOTE] Accept karaf-camel as new Apache Karaf subproject
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Feb 10, 2023 at 9:44 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
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 Camel "core" community doesn't want to maintain OSGi related
> stuff in camel-core.
>
> I propose the following:
>
> 1. We keep camel-karaf at Camel (as we have camel-quarkus,
> camel-spring-boot, ..., I hope we don't have anything in camel-core
> needed/required by camel-quarkus or camel-spring-boot, else it
> wouldn't be fair for camel-karaf ;) )
>
Yes, camel-core is independent/neutral. There is no Spring Boot, Quarkus,
etc dependency.
camel-karaf should be maintained and released by you and others who want
and can work on camel-karaf.
We have camel-k, camel-kafka-connector, camel-karvan, and camel-quarkus
that are done in such a way,
they are maintained and released by "teams".
The camel-core team does the core + SB release together.
SB is easy to maintain and by the most used runtime with Camel.
2. Camel Core can remove OSGi related stuff (headers,
> maven-bundle-plugin, ...), we will implement a new approach in
> camel-karaf (with a custom deployer as I proposed before for
> instance).
>
Yes. Looking back, I really wish that Karaf had such a deployment model 10
years ago, deploying plain JARs
and maven pom's (no need for OSGi metadata). Actually looking forward to
seeing what you come up with.
> 3. I will do a complete cleanup on the camel-karaf main branch,
> already upgrading to camel 4 to prepare camel-karaf 4.
>
>
Okay
> Thoughts ?
>
> Regards
> JB
>
--
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2