date:20240103

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Andrea Cosentino

It's fine for me. I think we should maybe improve the labels for all the
releases

Il mer 3 gen 2024, 17:29 Pasquale Congiusti 
ha scritto:

> Hi Marat,
> thanks for letting us know. I can see if I can remove it. However it's not
> a big deal since the dependency is only used for tooling purposes, so,
> having released ahead of time is not putting any kind of risk. If the rest
> of the community is okey with it, we can leave it and remove it if by any
> chance the release has to be canceled.
>
> Regards,
> Pasquale.
>
> On Wed, Jan 3, 2024 at 4:58 PM Marat Gubaidullin <
> marat.gubaidul...@gmail.com> wrote:
>
> > Hello,
> >
> > I made a huge mistake by accidentally releasing Camel K CRD Java
> dependency
> > 2.2.0.
> > I do not know how to roll back these changes in Apache Sonatype myself.
> > Please help, how to fix the situation.
> >
> > Sorry about that.
> >
> > Marat
> >
> > On Wed, Jan 3, 2024 at 4:43 AM Pasquale Congiusti <
> > pasquale.congiu...@gmail.com> wrote:
> >
> > > Hello,
> > >
> > > This is a vote to release Apache Camel K 2.2.0. This release provides
> new
> > > features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based
> > on
> > > Camel 4.0.3).
> > >
> > > * A previous release attempt was canceled on December 22nd 2023 due to
> > the
> > > fact that it was based on a non LTS Camel version.
> > >
> > > Camel K release files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
> > >
> > > Camel K Tag:
> > > https://github.com/apache/camel-k/releases/tag/v2.2.0
> > >
> > > Camel K CRD Java dependency staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
> > >
> > > Staging container image repository:
> > > AMD64 architecture:
> > >
> > >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> > > ARM64
> > > <
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=exploreARM64
> > >
> > > architecture (preview only):
> > >
> > >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
> > >
> > > It's possible to install all staging artifacts with a single command
> > > (preferably using the kamel CLI you find in Camel K release files):
> > >
> > > kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
> > >
> > > Please test this release candidate and cast your vote.
> > >
> > > [ ] +1 Release Apache Camel K 2.2.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > I start the vote with my +1.
> > >
> > > Thanks and regards,
> > > Pasquale Congiusti
> > >
> > > [1] https://github.com/apache/camel-k/milestone/47?closed=1
> > >
> >
>

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Pasquale Congiusti

Hi Marat,
thanks for letting us know. I can see if I can remove it. However it's not
a big deal since the dependency is only used for tooling purposes, so,
having released ahead of time is not putting any kind of risk. If the rest
of the community is okey with it, we can leave it and remove it if by any
chance the release has to be canceled.

Regards,
Pasquale.

On Wed, Jan 3, 2024 at 4:58 PM Marat Gubaidullin <
marat.gubaidul...@gmail.com> wrote:

> Hello,
>
> I made a huge mistake by accidentally releasing Camel K CRD Java dependency
> 2.2.0.
> I do not know how to roll back these changes in Apache Sonatype myself.
> Please help, how to fix the situation.
>
> Sorry about that.
>
> Marat
>
> On Wed, Jan 3, 2024 at 4:43 AM Pasquale Congiusti <
> pasquale.congiu...@gmail.com> wrote:
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.2.0. This release provides new
> > features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based
> on
> > Camel 4.0.3).
> >
> > * A previous release attempt was canceled on December 22nd 2023 due to
> the
> > fact that it was based on a non LTS Camel version.
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.2.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1666/
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> > ARM64
> > <
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=exploreARM64
> >
> > architecture (preview only):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.2.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/47?closed=1
> >
>

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Marat Gubaidullin

Hello,

I made a huge mistake by accidentally releasing Camel K CRD Java dependency
2.2.0.
I do not know how to roll back these changes in Apache Sonatype myself.
Please help, how to fix the situation.

Sorry about that.

Marat

On Wed, Jan 3, 2024 at 4:43 AM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.2.0. This release provides new
> features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
> Camel 4.0.3).
>
> * A previous release attempt was canceled on December 22nd 2023 due to the
> fact that it was based on a non LTS Camel version.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.2.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
>
> Staging container image repository:
> AMD64 architecture:
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> ARM64
> 
> architecture (preview only):
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/47?closed=1
>

[RESULT][VOTE] Release of Apache Camel Karavan 4.3.0

2024-01-03 Thread Marat Gubaidullin

Happy New Year, Camel Developers!

Thank you for your votes!

Vote results:
6: +1 binding votes: Claus Ibsen, Andrea Cosentino, Babak Vahdat, Nicolas
Filotto, Zineb Bendhiba, Jean-Baptiste Onofré
1: +1 non-binding vote: Marat Gubaidullin

I'll publish artifacts soon.

Marat

Re: Apache Camel 4.4 LTS release in February 2024

2024-01-03 Thread Otavio Rodolfo Piske

+1 from me.

I have a few more things to do for the Clock API and that's it on my end.

Kind regards

On Wed, Jan 3, 2024 at 10:25 AM Claus Ibsen  wrote:

> Hi
>
> The next LTS release is 4.4 that is planned for February 2024.
>
> For this release we have the usual bunch of dependency upgrades.
> The next Spring Boot 3.2.x release (later this month).
> And the Quarkus team is also waiting for a new Quarkus release to upgrade.
>
> I have some more work on the new variable stuff to complete.
> But I will be on PTO for 2 full weeks and will not be online, leaving
> tomorrow.
>
> The JIRA has some items listed. Fell free to move to 4.5 if there are
> tickets that you know we wont have time to implement or look at.
>
> And our CI server and tests are looking good. We have a very low number of
> test failures, but would be good to keep it low and get green builds more
> often.
>
> There is 1 test that keeps failing on Java 21 (there is a ticket about it).
>
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

RE: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Nicolas Filotto

+1 (binding)

De : Otavio Rodolfo Piske 
Envoyé : mercredi 3 janvier 2024 14:56
À : dev@camel.apache.org 
Objet : Re: [VOTE] Camel K 2.2.0 release *second attempt

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.



+1 (binding)

Thanks Pasquale!

On Wed, Jan 3, 2024 at 2:17 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks Pasquale!
>
> ---
> Gaëlle
>
> Le mer. 3 janv. 2024 à 10:43, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.2.0. This release provides new
> > features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based
> on
> > Camel 4.0.3).
> >
> > * A previous release attempt was canceled on December 22nd 2023 due to
> the
> > fact that it was based on a non LTS Camel version.
> >
> > Camel K release files:
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fcamel%2Fcamel-k%2F2.2.0%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=6TAJ540YZsSyBJgmtm63i97SAbfJSwe4fBK3Vdn6tVo%3D=0
> >
> > Camel K Tag:
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel-k%2Freleases%2Ftag%2Fv2.2.0=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oKlMOz0YvHpxD4yTGtXUffuUxZnX4klT5V%2BJ8plUSM0%3D=0
> >
> > Camel K CRD Java dependency staging repository:
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1666%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=FDa0g%2FBZac7r14D1cjrEmBl0aIXRHAxJN%2FydUpwh9NA%3D=0
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2Fcamelk%2Fcamel-k%2F2.2.0%2Fimages%2Fsha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e%3Fcontext%3Dexplore=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=Nn66%2Fv56JRUSlPhsJxq237KihfoQPQLiAbPWkR0Hr1s%3D=0
> > ARM64
> > <
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2Fcamelk%2Fcamel-k%2F2.2.0%2Fimages%2Fsha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e%3Fcontext%3DexploreARM64=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=cHnmgh2KRjgTIlZhIMymG1GBnPikVSK72Nz35Beg2nk%3D=0
> >
> > architecture (preview only):
> >
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2Fcamelk%2Fcamel-k%2F2.2.0-arm64%2Fimages%2Fsha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98%3Fcontext%3Dexplore=05%7C02%7CNicolas.Filotto%40qlik.com%7Cd47433f12b4e47aba2ac08dc0c63d914%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638398870180136315%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=4oz465iBel11Jjbusfwij2aSCgBbgjaHZyv1mSt0QUo%3D=0
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ]

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Otavio Rodolfo Piske

+1 (binding)

Thanks Pasquale!

On Wed, Jan 3, 2024 at 2:17 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks Pasquale!
>
> ---
> Gaëlle
>
> Le mer. 3 janv. 2024 à 10:43, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.2.0. This release provides new
> > features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based
> on
> > Camel 4.0.3).
> >
> > * A previous release attempt was canceled on December 22nd 2023 due to
> the
> > fact that it was based on a non LTS Camel version.
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.2.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1666/
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> > ARM64
> > <
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=exploreARM64
> >
> > architecture (preview only):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.2.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/47?closed=1
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Gaëlle Fournier

+1 (non-binding)

Thanks Pasquale!

---
Gaëlle

Le mer. 3 janv. 2024 à 10:43, Pasquale Congiusti <
pasquale.congiu...@gmail.com> a écrit :

> Hello,
>
> This is a vote to release Apache Camel K 2.2.0. This release provides new
> features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
> Camel 4.0.3).
>
> * A previous release attempt was canceled on December 22nd 2023 due to the
> fact that it was based on a non LTS Camel version.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.2.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
>
> Staging container image repository:
> AMD64 architecture:
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> ARM64
> 
> architecture (preview only):
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/47?closed=1
>

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Claus Ibsen

+1 (binding)

On Wed, Jan 3, 2024 at 10:43 AM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.2.0. This release provides new
> features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
> Camel 4.0.3).
>
> * A previous release attempt was canceled on December 22nd 2023 due to the
> fact that it was based on a non LTS Camel version.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.2.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
>
> Staging container image repository:
> AMD64 architecture:
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> ARM64
> 
> architecture (preview only):
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/47?closed=1
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Zineb Bendhiba

+1 (binding)

Le mer. 3 janv. 2024 à 10:43, Pasquale Congiusti <
pasquale.congiu...@gmail.com> a écrit :

> Hello,
>
> This is a vote to release Apache Camel K 2.2.0. This release provides new
> features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
> Camel 4.0.3).
>
> * A previous release attempt was canceled on December 22nd 2023 due to the
> fact that it was based on a non LTS Camel version.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.2.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
>
> Staging container image repository:
> AMD64 architecture:
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> ARM64
> 
> architecture (preview only):
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/47?closed=1
>


-- 
Zineb Bendhiba

Re: Adding JMX reporting and control to dynamic router eip component

2024-01-03 Thread Claus Ibsen

It needs to be added as a service.

in the producer you can do something ala

doStart

ControlService cs = new 
context.addService(cs);

And remove the service in doStop

See for example SendProcessor, or do a

git grep "addService("

And look in the code for other examples


On Wed, Jan 3, 2024 at 10:57 AM Steve973  wrote:

> An instance is created in the control producer.  How should it be created
> in order to be managed?
>
> On Wed, Jan 3, 2024, 3:59 AM Claus Ibsen  wrote:
>
> > Hi
> >
> > You should not overwrite start and stop methods. But implement doStart /
> > doStop if you need any logic.
> >
> > And how do you create DynamicRouterControlService in the first place
> >
> > On Tue, Jan 2, 2024 at 11:40 PM Steve973  wrote:
> >
> > > Hi, all.  I was talking about this on the users list, but I found out
> > about
> > > the dev list, so I wanted to share this question with fellow camel
> > > devs/contributors.
> > >
> > > I am adding JMX reporting and control to my dynamic router eip
> component
> > > (not the original dynamic router that you can use with the DSL in
> > core).  I
> > > have two services that I annotated with camel-management annotations:
> > >
> > > For JMX control (things removed for brevity):
> > >
> > > @Converter(generateBulkLoader = true)
> > > @ManagedResource(description = "Dynamic Router control operations
> > service")
> > > public class DynamicRouterControlService extends ServiceSupport {
> > >
> > > private final CamelContext camelContext;
> > >
> > > private final DynamicRouterFilterService filterService;
> > >
> > > public DynamicRouterControlService(CamelContext camelContext,
> > >DynamicRouterFilterService
> > > filterService) {
> > > this.camelContext = camelContext;
> > > this.filterService = filterService;
> > > }
> > >
> > > @ManagedOperation(description = "Subscribe for dynamic routing
> > > with a predicate expression")
> > > public String subscribeWithPredicateExpression(
> > > String subscribeChannel,
> > > String subscriptionId,
> > > String destinationUri,
> > > int priority,
> > > String predicate,
> > > String expressionLanguage,
> > > boolean update) {
> > > return filterService.addFilterForChannel(subscriptionId,
> > priority,
> > > obtainPredicateFromExpression(camelContext, predicate,
> > > expressionLanguage),
> > > destinationUri, subscribeChannel, update);
> > > }
> > >
> > > @ManagedOperation(description = "Subscribe for dynamic routing
> > > with the name of a predicate bean in the registry")
> > > public String subscribeWithPredicateBean(
> > > String subscribeChannel,
> > > String subscriptionId,
> > > String destinationUri,
> > > int priority,
> > > String predicateBean,
> > > boolean update) {
> > > return filterService.addFilterForChannel(subscriptionId,
> > priority,
> > > obtainPredicateFromBeanName(predicateBean,
> camelContext),
> > > destinationUri, subscribeChannel, update);
> > > }
> > >
> > > @ManagedOperation(description = "Subscribe for dynamic routing
> > > with a predicate instance")
> > > public String subscribeWithPredicateInstance(
> > > String subscribeChannel,
> > > String subscriptionId,
> > > String destinationUri,
> > > int priority,
> > > Object predicate,
> > > boolean update) {
> > > return filterService.addFilterForChannel(subscriptionId,
> > > priority, obtainPredicateFromInstance(predicate),
> > > destinationUri, subscribeChannel, update);
> > > }
> > >
> > > @ManagedOperation(description = "Unsubscribe for dynamic routing
> > > on a channel by subscription ID")
> > > public boolean removeSubscription(
> > > String subscribeChannel,
> > > String subscriptionId) {
> > > return filterService.removeFilterById(subscriptionId,
> > > subscribeChannel);
> > > }
> > >
> > > @Override
> > > public void start() {
> > > // no-op
> > > }
> > >
> > > @Override
> > > public void stop() {
> > > // no-op
> > > }
> > > }
> > >
> > > For reporting/monitoring (things removed for brevity):
> > >
> > > @ManagedResource(description = "Dynamic Router filter service")
> > > public class DynamicRouterFilterService extends ServiceSupport {
> > >
> > > private final Map > > ConcurrentSkipListSet> filterMap = new
> > > ConcurrentHashMap<>();
> > >
> > > private final Map>
> > > filterStatisticsMap = new ConcurrentHashMap<>();
> > >
> > > private final Supplier
> > filterFactorySupplier;
> > >
> > > public DynamicRouterFilterService(final
> > > Supplier filterFactorySupplier) {
> > >

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Claudio Miranda

+1 non binding




-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br

Re: Adding JMX reporting and control to dynamic router eip component

2024-01-03 Thread Steve973

An instance is created in the control producer.  How should it be created
in order to be managed?

On Wed, Jan 3, 2024, 3:59 AM Claus Ibsen  wrote:

> Hi
>
> You should not overwrite start and stop methods. But implement doStart /
> doStop if you need any logic.
>
> And how do you create DynamicRouterControlService in the first place
>
> On Tue, Jan 2, 2024 at 11:40 PM Steve973  wrote:
>
> > Hi, all.  I was talking about this on the users list, but I found out
> about
> > the dev list, so I wanted to share this question with fellow camel
> > devs/contributors.
> >
> > I am adding JMX reporting and control to my dynamic router eip component
> > (not the original dynamic router that you can use with the DSL in
> core).  I
> > have two services that I annotated with camel-management annotations:
> >
> > For JMX control (things removed for brevity):
> >
> > @Converter(generateBulkLoader = true)
> > @ManagedResource(description = "Dynamic Router control operations
> service")
> > public class DynamicRouterControlService extends ServiceSupport {
> >
> > private final CamelContext camelContext;
> >
> > private final DynamicRouterFilterService filterService;
> >
> > public DynamicRouterControlService(CamelContext camelContext,
> >DynamicRouterFilterService
> > filterService) {
> > this.camelContext = camelContext;
> > this.filterService = filterService;
> > }
> >
> > @ManagedOperation(description = "Subscribe for dynamic routing
> > with a predicate expression")
> > public String subscribeWithPredicateExpression(
> > String subscribeChannel,
> > String subscriptionId,
> > String destinationUri,
> > int priority,
> > String predicate,
> > String expressionLanguage,
> > boolean update) {
> > return filterService.addFilterForChannel(subscriptionId,
> priority,
> > obtainPredicateFromExpression(camelContext, predicate,
> > expressionLanguage),
> > destinationUri, subscribeChannel, update);
> > }
> >
> > @ManagedOperation(description = "Subscribe for dynamic routing
> > with the name of a predicate bean in the registry")
> > public String subscribeWithPredicateBean(
> > String subscribeChannel,
> > String subscriptionId,
> > String destinationUri,
> > int priority,
> > String predicateBean,
> > boolean update) {
> > return filterService.addFilterForChannel(subscriptionId,
> priority,
> > obtainPredicateFromBeanName(predicateBean, camelContext),
> > destinationUri, subscribeChannel, update);
> > }
> >
> > @ManagedOperation(description = "Subscribe for dynamic routing
> > with a predicate instance")
> > public String subscribeWithPredicateInstance(
> > String subscribeChannel,
> > String subscriptionId,
> > String destinationUri,
> > int priority,
> > Object predicate,
> > boolean update) {
> > return filterService.addFilterForChannel(subscriptionId,
> > priority, obtainPredicateFromInstance(predicate),
> > destinationUri, subscribeChannel, update);
> > }
> >
> > @ManagedOperation(description = "Unsubscribe for dynamic routing
> > on a channel by subscription ID")
> > public boolean removeSubscription(
> > String subscribeChannel,
> > String subscriptionId) {
> > return filterService.removeFilterById(subscriptionId,
> > subscribeChannel);
> > }
> >
> > @Override
> > public void start() {
> > // no-op
> > }
> >
> > @Override
> > public void stop() {
> > // no-op
> > }
> > }
> >
> > For reporting/monitoring (things removed for brevity):
> >
> > @ManagedResource(description = "Dynamic Router filter service")
> > public class DynamicRouterFilterService extends ServiceSupport {
> >
> > private final Map > ConcurrentSkipListSet> filterMap = new
> > ConcurrentHashMap<>();
> >
> > private final Map>
> > filterStatisticsMap = new ConcurrentHashMap<>();
> >
> > private final Supplier
> filterFactorySupplier;
> >
> > public DynamicRouterFilterService(final
> > Supplier filterFactorySupplier) {
> > this.filterFactorySupplier = filterFactorySupplier;
> > LOG.debug("Created Dynamic Router component");
> > }
> >
> > @ManagedAttribute(description = "Get the list of filters for the
> > specified dynamic router channel")
> > public Collection getFiltersForChannel(final
> > String channel) {
> > return List.copyOf(filterMap.get(channel));
> > }
> >
> > @ManagedAttribute(description = "Get the map of filters for all
> > dynamic router channels")
> > public Map>
> > getFilterMap() {
> > return Map.copyOf(filterMap);
> > }
> >
> >

Re: [VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Andrea Cosentino

+1 (binding)

Thanks Pasquale

Il mer 3 gen 2024, 10:43 Pasquale Congiusti 
ha scritto:

> Hello,
>
> This is a vote to release Apache Camel K 2.2.0. This release provides new
> features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
> Camel 4.0.3).
>
> * A previous release attempt was canceled on December 22nd 2023 due to the
> fact that it was based on a non LTS Camel version.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.2.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1666/
>
> Staging container image repository:
> AMD64 architecture:
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> ARM64
> 
> architecture (preview only):
>
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/47?closed=1
>

[VOTE] Camel K 2.2.0 release *second attempt

2024-01-03 Thread Pasquale Congiusti

Hello,

This is a vote to release Apache Camel K 2.2.0. This release provides new
features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based on
Camel 4.0.3).

* A previous release attempt was canceled on December 22nd 2023 due to the
fact that it was based on a non LTS Camel version.

Camel K release files:
https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/

Camel K Tag:
https://github.com/apache/camel-k/releases/tag/v2.2.0

Camel K CRD Java dependency staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1666/

Staging container image repository:
AMD64 architecture:
https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
ARM64 architecture (preview only):
https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore

It's possible to install all staging artifacts with a single command
(preferably using the kamel CLI you find in Camel K release files):

kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false

Please test this release candidate and cast your vote.

[ ] +1 Release Apache Camel K 2.2.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

I start the vote with my +1.

Thanks and regards,
Pasquale Congiusti

[1] https://github.com/apache/camel-k/milestone/47?closed=1

Re: Camel Kafka Connector - Releases

2024-01-03 Thread Andrea Cosentino

We can try that, but before that we need to add the SBOM generation and
pubblication.

I'll do that next week

Il mer 3 gen 2024, 10:19 Claus Ibsen  ha scritto:

> Hi
>
> I wonder if we can do a 4.0.3 LTS release of CKC to bring it up to latest
> patch release.
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Apache Camel 4.4 LTS release in February 2024

2024-01-03 Thread Claus Ibsen

Hi

The next LTS release is 4.4 that is planned for February 2024.

For this release we have the usual bunch of dependency upgrades.
The next Spring Boot 3.2.x release (later this month).
And the Quarkus team is also waiting for a new Quarkus release to upgrade.

I have some more work on the new variable stuff to complete.
But I will be on PTO for 2 full weeks and will not be online, leaving
tomorrow.

The JIRA has some items listed. Fell free to move to 4.5 if there are
tickets that you know we wont have time to implement or look at.

And our CI server and tests are looking good. We have a very low number of
test failures, but would be good to keep it low and get green builds more
often.

There is 1 test that keeps failing on Java 21 (there is a ticket about it).




-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Camel Kafka Connector - Releases

2024-01-03 Thread Claus Ibsen

Hi

I wonder if we can do a 4.0.3 LTS release of CKC to bring it up to latest
patch release.


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Adding JMX reporting and control to dynamic router eip component

2024-01-03 Thread Claus Ibsen

Hi

You should not overwrite start and stop methods. But implement doStart /
doStop if you need any logic.

And how do you create DynamicRouterControlService in the first place

On Tue, Jan 2, 2024 at 11:40 PM Steve973  wrote:

> Hi, all.  I was talking about this on the users list, but I found out about
> the dev list, so I wanted to share this question with fellow camel
> devs/contributors.
>
> I am adding JMX reporting and control to my dynamic router eip component
> (not the original dynamic router that you can use with the DSL in core).  I
> have two services that I annotated with camel-management annotations:
>
> For JMX control (things removed for brevity):
>
> @Converter(generateBulkLoader = true)
> @ManagedResource(description = "Dynamic Router control operations service")
> public class DynamicRouterControlService extends ServiceSupport {
>
> private final CamelContext camelContext;
>
> private final DynamicRouterFilterService filterService;
>
> public DynamicRouterControlService(CamelContext camelContext,
>DynamicRouterFilterService
> filterService) {
> this.camelContext = camelContext;
> this.filterService = filterService;
> }
>
> @ManagedOperation(description = "Subscribe for dynamic routing
> with a predicate expression")
> public String subscribeWithPredicateExpression(
> String subscribeChannel,
> String subscriptionId,
> String destinationUri,
> int priority,
> String predicate,
> String expressionLanguage,
> boolean update) {
> return filterService.addFilterForChannel(subscriptionId, priority,
> obtainPredicateFromExpression(camelContext, predicate,
> expressionLanguage),
> destinationUri, subscribeChannel, update);
> }
>
> @ManagedOperation(description = "Subscribe for dynamic routing
> with the name of a predicate bean in the registry")
> public String subscribeWithPredicateBean(
> String subscribeChannel,
> String subscriptionId,
> String destinationUri,
> int priority,
> String predicateBean,
> boolean update) {
> return filterService.addFilterForChannel(subscriptionId, priority,
> obtainPredicateFromBeanName(predicateBean, camelContext),
> destinationUri, subscribeChannel, update);
> }
>
> @ManagedOperation(description = "Subscribe for dynamic routing
> with a predicate instance")
> public String subscribeWithPredicateInstance(
> String subscribeChannel,
> String subscriptionId,
> String destinationUri,
> int priority,
> Object predicate,
> boolean update) {
> return filterService.addFilterForChannel(subscriptionId,
> priority, obtainPredicateFromInstance(predicate),
> destinationUri, subscribeChannel, update);
> }
>
> @ManagedOperation(description = "Unsubscribe for dynamic routing
> on a channel by subscription ID")
> public boolean removeSubscription(
> String subscribeChannel,
> String subscriptionId) {
> return filterService.removeFilterById(subscriptionId,
> subscribeChannel);
> }
>
> @Override
> public void start() {
> // no-op
> }
>
> @Override
> public void stop() {
> // no-op
> }
> }
>
> For reporting/monitoring (things removed for brevity):
>
> @ManagedResource(description = "Dynamic Router filter service")
> public class DynamicRouterFilterService extends ServiceSupport {
>
> private final Map ConcurrentSkipListSet> filterMap = new
> ConcurrentHashMap<>();
>
> private final Map>
> filterStatisticsMap = new ConcurrentHashMap<>();
>
> private final Supplier filterFactorySupplier;
>
> public DynamicRouterFilterService(final
> Supplier filterFactorySupplier) {
> this.filterFactorySupplier = filterFactorySupplier;
> LOG.debug("Created Dynamic Router component");
> }
>
> @ManagedAttribute(description = "Get the list of filters for the
> specified dynamic router channel")
> public Collection getFiltersForChannel(final
> String channel) {
> return List.copyOf(filterMap.get(channel));
> }
>
> @ManagedAttribute(description = "Get the map of filters for all
> dynamic router channels")
> public Map>
> getFilterMap() {
> return Map.copyOf(filterMap);
> }
>
> @ManagedAttribute(description = "Get the set of filter statistics
> for the specified dynamic router channel")
> public List
> getStatisticsForChannel(final String channel) {
> return List.copyOf(filterStatisticsMap.get(channel));
> }
>
> @ManagedAttribute(description = "Get the map of statistics for all
> dynamic router channels")
> public Map>
> getFilterStatisticsMap() {
> return

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

[RESULT][VOTE] Release of Apache Camel Karavan 4.3.0

Re: Apache Camel 4.4 LTS release in February 2024

RE: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: Adding JMX reporting and control to dynamic router eip component

Re: [VOTE] Camel K 2.2.0 release *second attempt

Re: Adding JMX reporting and control to dynamic router eip component

Re: [VOTE] Camel K 2.2.0 release *second attempt

[VOTE] Camel K 2.2.0 release *second attempt

Re: Camel Kafka Connector - Releases

Apache Camel 4.4 LTS release in February 2024

Camel Kafka Connector - Releases

Re: Adding JMX reporting and control to dynamic router eip component

19 matches

Site Navigation

Mail list logo

Footer information