Re: [VOTE] Release Apache Camel Quarkus 3.8.2
+1 (binding) On Tue, Apr 30, 2024 at 1:15 PM James Netherton wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.8.2 LTS. > > Highlights: > > * Camel 4.4.2 > * Quarkus 3.8.4 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.8.1...3.8.2 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1708 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.8.2 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.8.2/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.8.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.4.2
+1 (binding) On Tue, Apr 30, 2024 at 10:52 AM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.4.2 > > This is a release supporting Camel 4.4.2 and it's an LTS release. > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.2 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1707 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.4.2 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.4.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: camel-karaf is back
On Tue, Apr 30, 2024 at 10:21 AM James Netherton wrote: > There's no 'docs' directory on the main branch, which causes the > camel-website build to fail. > > If there's no objection, I'll temporarily remove 'main' from the Antora > config for camel-karaf until that gets fixed. > > > https://github.com/apache/camel-website/blob/main/antora-playbook-snippets/antora-playbook.yml#L87 > > Yes do that, and main should only be added back when camel-karaf has its docs fixed and ready to go for publishing on the shared camel website. > -- > James > > On Mon, 29 Apr 2024 at 20:22, Jean-Baptiste Onofré > wrote: > > > Hey Claus > > > > Yeah that’s the plan : use GH issues and resources like the other Camel > > projects do. > > Jira can be dedicated for core. > > > > Thanks ! > > > > Regards > > JB > > > > Le lun. 29 avr. 2024 à 16:40, Claus Ibsen a > écrit > > : > > > > > Hi JB > > > > > > Okay thanks for the heads-up. It has been a long run and work for you > > guys. > > > > > > The camel-karaf team should be responsible for maintaining, bug fixing > > and > > > releasing camel-karaf independently, just like camel-quarkus, camel-k, > > > camel-karavan does. > > > We should consider opening camel-karaf github issue tracker so > > camel-karaf > > > users and developers can use this to track bugs and other issues. > > > That avoids polluting the old CAMEL jira that is for the core project. > > > > > > > > > > > > On Mon, Apr 29, 2024 at 3:22 PM Jean-Baptiste Onofré > > > wrote: > > > > > > > Hi folks, > > > > > > > > FYI, camel-karaf main branch has been updated with: > > > > - all Karaf core bundles for Camel 4.5.x > > > > - a lot of component wrappers for Camel 4.5.x > > > > - updated Karaf features repository > > > > - the infra resources (labeler, dependabot, etc) > > > > > > > > I plan a release soon (RC0) as soon as I push the new shell commands > > > > (in progress). > > > > > > > > The tests and examples will be completed including the shell > commands. > > > > > > > > You can use GH Issues for camel-karaf now: > > > > > > > > https://github.com/apache/camel-karaf > > > > > > > > Stay tuned for updates ! > > > > > > > > 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
Re: [VOTE] Release Apache Camel K 2.3.1
+1 (binding) On Mon, Apr 29, 2024 at 4:01 PM Pasquale Congiusti < pasquale.congiu...@gmail.com> wrote: > Hello, > > This is a vote to release Apache Camel K 2.3.1. This release provides some > bug fixes reported in the latest release 2.3.0 [1] due to certain changes > in Knative resources. > > Camel K release files: > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.1/ > > Camel K Tag: > https://github.com/apache/camel-k/releases/tag/v2.3.1 > > Camel K CRD Java dependency staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1703/ > > Staging container image repository (multi architecture manifest): > > https://hub.docker.com/layers/camelk/camel-k/2.3.1/images/sha256-8ab1a1cb911c7455393231eec0b1f8f5a75b1bafac6fa7d3cd5f186f3a5510b0?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.3.1 --olm=false > > Please test this release candidate and cast your vote. > > [ ] +1 Release Apache Camel K 2.3.1 > [ ] -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/50?closed=1 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: camel-karaf is back
Hi JB Okay thanks for the heads-up. It has been a long run and work for you guys. The camel-karaf team should be responsible for maintaining, bug fixing and releasing camel-karaf independently, just like camel-quarkus, camel-k, camel-karavan does. We should consider opening camel-karaf github issue tracker so camel-karaf users and developers can use this to track bugs and other issues. That avoids polluting the old CAMEL jira that is for the core project. On Mon, Apr 29, 2024 at 3:22 PM Jean-Baptiste Onofré wrote: > Hi folks, > > FYI, camel-karaf main branch has been updated with: > - all Karaf core bundles for Camel 4.5.x > - a lot of component wrappers for Camel 4.5.x > - updated Karaf features repository > - the infra resources (labeler, dependabot, etc) > > I plan a release soon (RC0) as soon as I push the new shell commands > (in progress). > > The tests and examples will be completed including the shell commands. > > You can use GH Issues for camel-karaf now: > > https://github.com/apache/camel-karaf > > Stay tuned for updates ! > > Regards > JB > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 3.22.2 Release
Hi Gregor Okay the 3.22.x branch is ready for cutting a release. On Thu, Apr 25, 2024 at 12:37 PM Claus Ibsen wrote: > > > On Thu, Apr 25, 2024 at 12:15 PM Gregor Zurowski > wrote: > >> Hi, >> >> I am definitely not bored but will be available for cutting the 3.22.2 >> release this week. :) >> >> > Okay thanks. I will check the branch and report back when its ready > > >> Thanks, >> Gregor >> >> On Thu, Apr 25, 2024 at 9:42 AM Claus Ibsen >> wrote: >> > >> > Hi >> > >> > It's been a while since we did 3.22.1. So it would be good to get a new >> > patch release out. >> > >> > Gregor if you are listening and "bored" then you are welcome to let us >> know >> > if you have time and want to cut a release. Then we can do a sanity >> check >> > on the branch and make sure its ready for you to go. >> > >> > PS: For 3.21.5 then we can wait a bit more as its the last planned patch >> > release and 3.21.x will be EOL in a few months. >> > >> > >> > >> > -- >> > Claus Ibsen >> > - >> > @davsclaus >> > Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 3.22.2 Release
On Thu, Apr 25, 2024 at 12:15 PM Gregor Zurowski wrote: > Hi, > > I am definitely not bored but will be available for cutting the 3.22.2 > release this week. :) > > Okay thanks. I will check the branch and report back when its ready > Thanks, > Gregor > > On Thu, Apr 25, 2024 at 9:42 AM Claus Ibsen wrote: > > > > Hi > > > > It's been a while since we did 3.22.1. So it would be good to get a new > > patch release out. > > > > Gregor if you are listening and "bored" then you are welcome to let us > know > > if you have time and want to cut a release. Then we can do a sanity check > > on the branch and make sure its ready for you to go. > > > > PS: For 3.21.5 then we can wait a bit more as its the last planned patch > > release and 3.21.x will be EOL in a few months. > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel 3.22.2 Release
Hi It's been a while since we did 3.22.1. So it would be good to get a new patch release out. Gregor if you are listening and "bored" then you are welcome to let us know if you have time and want to cut a release. Then we can do a sanity check on the branch and make sure its ready for you to go. PS: For 3.21.5 then we can wait a bit more as its the last planned patch release and 3.21.x will be EOL in a few months. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel 4.6 Release in May
Hi I think it would be good to get a 4.6 (non LTS) release out early next month. Lets try to get bits ready by the end of next week. And if not then we can move out one week. For Camel SB on 4.5 then they have a bit of annoying bug in camel-micrometer that would make it easier if they can get hands on 4.6. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Quarkus 3.10.0
+1 (binding) On Wed, Apr 24, 2024 at 3:27 PM James Netherton wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.10.0. > > Highlights: > > * Camel 4.5.0 > * Quarkus 3.10.0 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.9.0...3.10.0 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1701 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.10.0 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.10.0/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.10.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.0.5 (LTS)
+1 (binding) On Tue, Apr 23, 2024 at 10:01 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.0.5, a new patch release with > 18 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353858=12311211 > > == Apache Camel 4.0.5 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1698/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1698/org/apache/camel/camel/4.0.5/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.5 > > == Apache Camel Spring Boot 4.0.5 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1699/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1699/org/apache/camel/springboot/spring-boot/4.0.5/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.5 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.5 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.4.2 (LTS)
+1 (binding) On Sun, Apr 21, 2024 at 7:48 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.4.2, a new patch release with > 31 fixes and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354402=12311211 > > == Apache Camel 4.4.2 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1695/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1695/org/apache/camel/apache-camel/4.4.2/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.2 > > == Apache Camel Spring Boot 4.4.2 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1696/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.2 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.0.5 Release in May
Okay the 4.0.x branch is also ready for releasing 4.0.5. On Fri, Apr 19, 2024 at 2:47 PM Otavio Rodolfo Piske wrote: > +1 from me. > > Thanks! > > On Fri, Apr 19, 2024 at 9:46 AM Andrea Cosentino > wrote: > > > +1 from my side. > > --Andrea Cosentino --Apache Camel PMC > > ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: > > ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd > > > > On Thursday, April 18, 2024 at 10:27:47 PM GMT+2, Claus Ibsen < > > claus.ib...@gmail.com> wrote: > > > > Hi > > > > After the 4.4.2 release, we could just as well do a patch release for > > 4.0.5. > > We have upgraded to the latest spring boot and the branch is also ready > for > > cutting a release. > > > > > > > > -- > > Claus Ibsen > > ----- > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > -- > Otavio R. Piske > http://orpiske.net > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.4.2 release by end of April
Hi Okay the 4.4.x branch is ready for releasing 4.4.2. On Thu, Apr 18, 2024 at 8:57 PM Claus Ibsen wrote: > Hi > > Okay so we have just upgraded to Spring Boot 3.2.5 on the 4.4.x branch. > So lets give the CI server the night to do a build and test, and tomorrow > (friday) we can give the GO for Gregor to build the release. > > On Tue, Apr 16, 2024 at 2:52 PM Claus Ibsen wrote: > >> >> >> On Tue, Apr 16, 2024 at 12:29 PM Tom Cunningham >> wrote: >> >>> I think spring-boot 3.2.5 is coming out on Thursday - is there enough >>> time >>> to get an upgrade to that in before the release? >>> >>> >> Yes, will we update to the latest SB. We aim to have the branch ready >> Friday noon for Gregor to build the release aftwards / over the weekend. >> >> >>> On Tue, Apr 16, 2024 at 4:35 AM Gregor Zurowski < >>> gre...@list.zurowski.org> >>> wrote: >>> >>> > I am back and available for cutting the release next weekend if we get >>> > everything in by then. >>> > >>> > Thanks, >>> > Gregor >>> > >>> > On Mon, Apr 15, 2024 at 6:50 AM Claus Ibsen >>> wrote: >>> > > >>> > > Hi >>> > > >>> > > I think it would be good to get this branch ready this week, so >>> Gregor >>> > can >>> > > cut the release when he has time. >>> > > >>> > > >>> > > On Fri, Mar 29, 2024 at 6:57 PM Claus Ibsen >>> > wrote: >>> > > >>> > > > Hi >>> > > > >>> > > > I think it would be good to cut a new 4.4.2 LTS patch to be >>> released >>> > > > towards the end of April. >>> > > > Gregor is out of town for 2 weeks, so that should be okay. When he >>> > returns >>> > > > we can bring him into the loop of finding time to cut this release. >>> > > > >>> > > > >>> > > > -- >>> > > > Claus Ibsen >>> > > > - >>> > > > @davsclaus >>> > > > Camel in Action 2: https://www.manning.com/ibsen2 >>> > > > >>> > > >>> > > >>> > > -- >>> > > Claus Ibsen >>> > > - >>> > > @davsclaus >>> > > Camel in Action 2: https://www.manning.com/ibsen2 >>> > >>> > >>> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel 4.0.5 Release in May
Hi After the 4.4.2 release, we could just as well do a patch release for 4.0.5. We have upgraded to the latest spring boot and the branch is also ready for cutting a release. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.4.2 release by end of April
Hi Okay so we have just upgraded to Spring Boot 3.2.5 on the 4.4.x branch. So lets give the CI server the night to do a build and test, and tomorrow (friday) we can give the GO for Gregor to build the release. On Tue, Apr 16, 2024 at 2:52 PM Claus Ibsen wrote: > > > On Tue, Apr 16, 2024 at 12:29 PM Tom Cunningham > wrote: > >> I think spring-boot 3.2.5 is coming out on Thursday - is there enough time >> to get an upgrade to that in before the release? >> >> > Yes, will we update to the latest SB. We aim to have the branch ready > Friday noon for Gregor to build the release aftwards / over the weekend. > > >> On Tue, Apr 16, 2024 at 4:35 AM Gregor Zurowski > > >> wrote: >> >> > I am back and available for cutting the release next weekend if we get >> > everything in by then. >> > >> > Thanks, >> > Gregor >> > >> > On Mon, Apr 15, 2024 at 6:50 AM Claus Ibsen >> wrote: >> > > >> > > Hi >> > > >> > > I think it would be good to get this branch ready this week, so Gregor >> > can >> > > cut the release when he has time. >> > > >> > > >> > > On Fri, Mar 29, 2024 at 6:57 PM Claus Ibsen >> > wrote: >> > > >> > > > Hi >> > > > >> > > > I think it would be good to cut a new 4.4.2 LTS patch to be released >> > > > towards the end of April. >> > > > Gregor is out of town for 2 weeks, so that should be okay. When he >> > returns >> > > > we can bring him into the loop of finding time to cut this release. >> > > > >> > > > >> > > > -- >> > > > Claus Ibsen >> > > > - >> > > > @davsclaus >> > > > Camel in Action 2: https://www.manning.com/ibsen2 >> > > > >> > > >> > > >> > > -- >> > > Claus Ibsen >> > > - >> > > @davsclaus >> > > Camel in Action 2: https://www.manning.com/ibsen2 >> > >> > >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.4.2 release by end of April
On Tue, Apr 16, 2024 at 12:29 PM Tom Cunningham wrote: > I think spring-boot 3.2.5 is coming out on Thursday - is there enough time > to get an upgrade to that in before the release? > > Yes, will we update to the latest SB. We aim to have the branch ready Friday noon for Gregor to build the release aftwards / over the weekend. > On Tue, Apr 16, 2024 at 4:35 AM Gregor Zurowski > wrote: > > > I am back and available for cutting the release next weekend if we get > > everything in by then. > > > > Thanks, > > Gregor > > > > On Mon, Apr 15, 2024 at 6:50 AM Claus Ibsen > wrote: > > > > > > Hi > > > > > > I think it would be good to get this branch ready this week, so Gregor > > can > > > cut the release when he has time. > > > > > > > > > On Fri, Mar 29, 2024 at 6:57 PM Claus Ibsen > > wrote: > > > > > > > Hi > > > > > > > > I think it would be good to cut a new 4.4.2 LTS patch to be released > > > > towards the end of April. > > > > Gregor is out of town for 2 weeks, so that should be okay. When he > > returns > > > > we can bring him into the loop of finding time to cut this release. > > > > > > > > > > > > -- > > > > Claus Ibsen > > > > - > > > > @davsclaus > > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release of Apache Camel Karavan 4.5.0
+1 (binding) On Sun, Apr 14, 2024 at 10:40 PM Marat Gubaidullin < marat.gubaidul...@gmail.com> wrote: > Dear Camel Developers, > > This is a vote for the release of Apache Camel Karavan version 4.5.0. > > Developer Experience improvements: > >1. List of Exchange Properties for EIP in Properties Panel >2. Exchange Variables and Functions docs for mostly used Expression >Languages in Editor >3. During installation Templates created only for the container >management used (Docker, Kubernetes, Openshift) >4. Automatic created ConfigMaps for build script in Kubernetes >5. Preferred Element in Component/Kamelet/EIP Palette (more used = >preferred) >6. User can delete Preferred Element in Component/Kamelet/EIP Palette >7. In devmode Trace window contains Exchange Body, Headers, Properties >and variables > > Latest versions: > >1. Camel 4.5.0 >2. Kamelets 4.5.0 >3. Jkube 1.16.2 >4. JBang v0.116.0 > > Source release package: > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.5.0/ > > Some files in the codebase have missing licence headers still. This is done > intentionally, because these files are code snippets/templates used to > generate user's code. > > VS Code Extension > https://github.com/apache/camel-karavan/releases/tag/4.5.0 > > We encourage all Camel contributors to participate in this release vote. > Your feedback and contributions play a crucial role in making Apache Camel > Karavan better with each release. > > Please cast your vote by replying to this email with your decision: > [ ] +1 Release > [ ] -1 Veto the release (provide specific comments) > > The voting period will remain open for 72 hours. > > Thank you for your continued support and dedication to the Apache Camel > project. > > My +1 is here > > Have a nice day, > Marat > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.4.2 release by end of April
Hi I think it would be good to get this branch ready this week, so Gregor can cut the release when he has time. On Fri, Mar 29, 2024 at 6:57 PM Claus Ibsen wrote: > Hi > > I think it would be good to cut a new 4.4.2 LTS patch to be released > towards the end of April. > Gregor is out of town for 2 weeks, so that should be okay. When he returns > we can bring him into the loop of finding time to cut this release. > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel K 2.3.0
+1 (binding) On Tue, Apr 2, 2024 at 4:46 PM Pasquale Congiusti < pasquale.congiu...@gmail.com> wrote: > Hello, > > This is a vote to release Apache Camel K 2.3.0. This release provides many > new features [1] and sets the default runtime to Camel Quarkus 3.8.1 (based > on Camel 4.4.1). > > Camel K release files: > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.0/ > > Camel K Tag: > https://github.com/apache/camel-k/releases/tag/v2.3.0 > > Camel K CRD Java dependency staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1693/ > > Staging container image repository (multi architecture manifest): > > https://hub.docker.com/layers/camelk/camel-k/2.3.0/images/sha256-a043af04c9b816f0dfd5db64ba69bae192d73dd726df83aaf2002559a111a786?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.3.0 --olm=false > > Please test this release candidate and cast your vote. > > [ ] +1 Release Apache Camel K 2.3.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/48?closed=1 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.5.0
+1 (binding) On Tue, Apr 2, 2024 at 7:47 AM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.5.0 > > This is a release supporting Camel 4.5.0 and it's a development release. > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.5.0 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1692 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.5.0 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.5.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel Support for EDIFACT DATA Format
Hi see the smooks project they have edi and camel Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2 fre. 29. mar. 2024 kl. 22.38 skrev Mohamed Chebbi < mohamed.sadok.che...@gmail.com>: > Hi all > > Does Camel have a support for edifact data format? > > EDIFACT is widely used in the Telecom industry essentially in provisioning. > > Best regards > Mohamed Chebbo >
Camel 4.4.2 release by end of April
Hi I think it would be good to cut a new 4.4.2 LTS patch to be released towards the end of April. Gregor is out of town for 2 weeks, so that should be okay. When he returns we can bring him into the loop of finding time to cut this release. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel Kamelets 4.5.0 Release
Hi I think it would be good to get a 4.5.0 release of kamelets as well, now that core is going to be released very soon. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.5.0
Morning Gregor I wonder if this VOTE can be closed and Camel released, thanks. On Sun, Mar 24, 2024 at 11:00 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.5.0, a new LTS release with > 151 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354104=12311211 > > == Apache Camel 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1689/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1689/org/apache/camel/apache-camel/4.5.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.5.0 > > == Apache Camel Spring Boot 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1690/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.5.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.5.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Possible improvement for using Apache PLC4X in Karavan
Hi There is also a discussion about karavan at which is more active and more focused on karavan https://github.com/apache/camel-karavan/discussions On Mon, Mar 25, 2024 at 1:38 PM Christofer Dutz wrote: > Hi all, > > So, in the last few months we have worked really hard on exposing a lot of > information about PLC4X drivers and connections to tools using it. > With these changes you can now provide a lot of assistance for configuring > PLC connections with PLC4X. > I remember that in Karavan you had to manually write a PLC4X connection > string in order to setup a PLC as source or sink. > Now theoretically it should be possible to build an editor, that > automatically knows for which driver, wich options are available, which are > defaults and so on. > With the manual connection-string writing much could go wrong, with our > latest changes things could be a lot simpler. > > Would Karavan be able to provide dynamic, possibly wizard-style > configurations of sources or sinks? > > Chris > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Camel K Runtime 3.8.1
+1 (binding) On Mon, Mar 25, 2024 at 12:14 PM Pasquale Congiusti < pasquale.congiu...@gmail.com> wrote: > Hello, > > This is a vote to release Camel K Runtime 3.8.1. This release will provide > the runtime for Camel Quarkus 3.8.1 (based on Camel 4.4.1) and include a > change in the catalog which will allow the Camel K Operator to be > completely independent from the runtime for the trait configuration. > > Camel K Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.8.1/ > > Camel K Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1691 > > Camel K Runtime Tag: > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.8.1 > > It's possible test the staging artifacts by installing the latest Camel K > CLI (kamel) with the staging repository and run any Integration with the > new runtime: > > - > kamel install --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1691 > ... > > kamel run Test.java -t camel.runtime-version=3.8.1 > - > > Please test these release candidates and cast your vote. > > [ ] +1 Release Apache Camel K Runtime 3.8.1 > [ ] -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 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.5.0
Hi I created a draft blog for whats new in 4.5. Feel free to add more content, feedback etc in the GH issue https://github.com/apache/camel-website/pull/1163 On Sun, Mar 24, 2024 at 11:00 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.5.0, a new LTS release with > 151 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354104=12311211 > > == Apache Camel 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1689/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1689/org/apache/camel/apache-camel/4.5.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.5.0 > > == Apache Camel Spring Boot 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1690/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.5.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.5.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.5.0
+1 (binding) On Sun, Mar 24, 2024 at 11:00 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.5.0, a new LTS release with > 151 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354104=12311211 > > == Apache Camel 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1689/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1689/org/apache/camel/apache-camel/4.5.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.5.0 > > == Apache Camel Spring Boot 4.5.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1690/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.5.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.5.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.5 Release
Hi Gregor The branches are ready for cutting the release. Good luck. On Thu, Mar 21, 2024 at 9:23 AM Gregor Zurowski wrote: > Hi, > > Yes, I'll be available for the release. Do you think we can start this > weekend? > > Thanks, > Gregor > > On Wed, Mar 20, 2024 at 5:18 PM Claus Ibsen wrote: > > > > Hi > > > > Okay lets close down the next couple of days to get the code ready for > > cutting 4.5.0 release. > > Gregor are you able to do this in the near future? > > > > > > > > On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen > wrote: > > > > > Hi > > > > > > We have good progress on the next minor release. > > > There is some work ongoing to simplify the maintenance of our generator > > > code we use during building Camel. After this is complete, and maybe > some > > > other stuff, then it would be good to get a 4.5.0 release out to the > > > community. > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----- > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.5 Release
Hi Okay we are doing the final checks before we are ready. On Thu, Mar 21, 2024 at 4:36 PM Claus Ibsen wrote: > Hi > > Okay we have upgraded to spring boot 3.2.4. > Also we have fixed code formatting, license checks and whatnot. > Looking good. We will get back to you tomorrow morning. > > On Thu, Mar 21, 2024 at 9:39 AM Claus Ibsen wrote: > >> Hi Gregor >> >> Yes that is very good. Later today Spring Boot 3.2.4 is released which we >> should upgrade. >> I will tidy up the last bits today, and give an update tomorrow when we >> are ready. >> >> >> >> On Thu, Mar 21, 2024 at 9:23 AM Gregor Zurowski >> wrote: >> >>> Hi, >>> >>> Yes, I'll be available for the release. Do you think we can start this >>> weekend? >>> >>> Thanks, >>> Gregor >>> >>> On Wed, Mar 20, 2024 at 5:18 PM Claus Ibsen >>> wrote: >>> > >>> > Hi >>> > >>> > Okay lets close down the next couple of days to get the code ready for >>> > cutting 4.5.0 release. >>> > Gregor are you able to do this in the near future? >>> > >>> > >>> > >>> > On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen >>> wrote: >>> > >>> > > Hi >>> > > >>> > > We have good progress on the next minor release. >>> > > There is some work ongoing to simplify the maintenance of our >>> generator >>> > > code we use during building Camel. After this is complete, and maybe >>> some >>> > > other stuff, then it would be good to get a 4.5.0 release out to the >>> > > community. >>> > > >>> > > >>> > > >>> > > -- >>> > > Claus Ibsen >>> > > - >>> > > @davsclaus >>> > > Camel in Action 2: https://www.manning.com/ibsen2 >>> > > >>> > >>> > >>> > -- >>> > Claus Ibsen >>> > - >>> > @davsclaus >>> > Camel in Action 2: https://www.manning.com/ibsen2 >>> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Quarkus 3.9.0
+1 (binding) On Thu, Mar 21, 2024 at 4:00 PM Alexandre Gallice wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.9.0. > > Highlights: > > * Camel 4.4.1 > * Quarkus 3.9.0 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.8.0...3.9.0 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1686 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.9.0 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.9.0/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.9.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.4.1
+1 (binding) On Fri, Mar 22, 2024 at 7:05 AM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.4.1 > > This is the second release of camel-kamelets supporting LTS Camel 4.4.x and > it contains alignment to 4.4.1 and some fixes. > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.1 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1687 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.4.1 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.4.1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel Kamelets 4.4.1 release
Hi We may want to do a 4.4.1 release so we can sync up with latest 4.4.x LTS release. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.5 Release
Hi Okay we have upgraded to spring boot 3.2.4. Also we have fixed code formatting, license checks and whatnot. Looking good. We will get back to you tomorrow morning. On Thu, Mar 21, 2024 at 9:39 AM Claus Ibsen wrote: > Hi Gregor > > Yes that is very good. Later today Spring Boot 3.2.4 is released which we > should upgrade. > I will tidy up the last bits today, and give an update tomorrow when we > are ready. > > > > On Thu, Mar 21, 2024 at 9:23 AM Gregor Zurowski > wrote: > >> Hi, >> >> Yes, I'll be available for the release. Do you think we can start this >> weekend? >> >> Thanks, >> Gregor >> >> On Wed, Mar 20, 2024 at 5:18 PM Claus Ibsen >> wrote: >> > >> > Hi >> > >> > Okay lets close down the next couple of days to get the code ready for >> > cutting 4.5.0 release. >> > Gregor are you able to do this in the near future? >> > >> > >> > >> > On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen >> wrote: >> > >> > > Hi >> > > >> > > We have good progress on the next minor release. >> > > There is some work ongoing to simplify the maintenance of our >> generator >> > > code we use during building Camel. After this is complete, and maybe >> some >> > > other stuff, then it would be good to get a 4.5.0 release out to the >> > > community. >> > > >> > > >> > > >> > > -- >> > > Claus Ibsen >> > > - >> > > @davsclaus >> > > Camel in Action 2: https://www.manning.com/ibsen2 >> > > >> > >> > >> > -- >> > Claus Ibsen >> > - >> > @davsclaus >> > Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.5 Release
Hi Gregor Yes that is very good. Later today Spring Boot 3.2.4 is released which we should upgrade. I will tidy up the last bits today, and give an update tomorrow when we are ready. On Thu, Mar 21, 2024 at 9:23 AM Gregor Zurowski wrote: > Hi, > > Yes, I'll be available for the release. Do you think we can start this > weekend? > > Thanks, > Gregor > > On Wed, Mar 20, 2024 at 5:18 PM Claus Ibsen wrote: > > > > Hi > > > > Okay lets close down the next couple of days to get the code ready for > > cutting 4.5.0 release. > > Gregor are you able to do this in the near future? > > > > > > > > On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen > wrote: > > > > > Hi > > > > > > We have good progress on the next minor release. > > > There is some work ongoing to simplify the maintenance of our generator > > > code we use during building Camel. After this is complete, and maybe > some > > > other stuff, then it would be good to get a 4.5.0 release out to the > > > community. > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----- > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.5 Release
Hi Okay lets close down the next couple of days to get the code ready for cutting 4.5.0 release. Gregor are you able to do this in the near future? On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen wrote: > Hi > > We have good progress on the next minor release. > There is some work ongoing to simplify the maintenance of our generator > code we use during building Camel. After this is complete, and maybe some > other stuff, then it would be good to get a 4.5.0 release out to the > community. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Catalog of pojo beans in the various camel components
Hi Okay so we have first set of pojo beans in the camel-catalog for almost all of the out-of-the-box: - aggregation strategy - aggregation repository - idempotent repository Some of these beans would need a bit more tooling friendly configuration, and this is something we can work on the next couple of releases. We can also use this when we find other beans that you may want to use with Camel such as RoutePolicy beans. And then markup those as well for inclusion in the catalog. To do that you add @Metadata(label = "bean") on the class (search in code for existing and see how its done) On Thu, Mar 14, 2024 at 10:09 PM Claus Ibsen wrote: > Hi > > https://issues.apache.org/jira/browse/CAMEL-17641 > > For some camel EIPs and components you can use aggregation strategy, > idempotent repository and other kind of beans that Camel provides a API for. > > To configure and use these beans then you often would need to find a doc > snippet that has an example. And maybe also dive into the source code. > > So I started to mark up these beans that we have in all the components, > and then to include metadata about these in camel-catalog. > > This allows us to put these in the docs, and make better tooling that can > tap into the catalog to know what comes from ASF Camel. > > The PR is a first prototype with some beans marked up from core, and > camel-zipfile. > https://github.com/apache/camel/pull/13491 > > But there are potentially 30-50 more beans we need to find and markup, and > also make sure they are pojo configure friendly with getter/setters. > > > > -- > Claus Ibsen > ----- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Quarkus 3.8.1
+1 (binding) On Fri, Mar 15, 2024 at 10:53 PM James Netherton wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.8.1. > > Highlights: > > * Camel 4.4.1 > * Quarkus 3.8.3 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.8.0...3.8.1 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1685 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.8.1 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.8.1/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.8.1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
[HEADS UP] - Catalog of pojo beans in the various camel components
Hi https://issues.apache.org/jira/browse/CAMEL-17641 For some camel EIPs and components you can use aggregation strategy, idempotent repository and other kind of beans that Camel provides a API for. To configure and use these beans then you often would need to find a doc snippet that has an example. And maybe also dive into the source code. So I started to mark up these beans that we have in all the components, and then to include metadata about these in camel-catalog. This allows us to put these in the docs, and make better tooling that can tap into the catalog to know what comes from ASF Camel. The PR is a first prototype with some beans marked up from core, and camel-zipfile. https://github.com/apache/camel/pull/13491 But there are potentially 30-50 more beans we need to find and markup, and also make sure they are pojo configure friendly with getter/setters. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Released BOM should have hardcoded camel version
Hi
The BOM should use hardcoded versions as the BOM is for a given version, eg
4.5.0 should be 4.5.0 versions.
That is also what everyone else is doing also. If you want to use a
different Camel version you refer to that BOM version, i.e. 4.6.0 and so on.
For example SB has 3.2.3 hardcoded in their 3.2.3 BOM file
https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/3.2.3/spring-boot-dependencies-3.2.3.pom
On Tue, Mar 12, 2024 at 2:45 PM Matt Pavlovich wrote:
> Hi Claus-
>
> Question: I’m planning to update some BOMs for other projects and was
> wondering if there were other reasons to use a hard-coded value vs a
> property? I agree, using ${project.version} is not going to work for a bom.
>
> Would using a declared property such as ${apache.camel.version} have any
> unintended side-effects?
>
> Thanks,
> Matt Pavlovich
>
> > On Mar 10, 2024, at 7:34 AM, Claus Ibsen wrote:
> >
> > Hi
> >
> > https://issues.apache.org/jira/browse/CAMEL-20413
> >
> > The BOM we release for both core and SB have
> >
> >
> > org.apache.camel
> > camel-api
> > ${project.version}
> >
> >
> > But they should use the hardcoded release version, eg:
> >
> >
> > org.apache.camel
> > camel-api
> > 4.4.0
> >
> >
> > If you look what we do now its wrong
> >
> https://repo1.maven.org/maven2/org/apache/camel/camel-bom/4.4.0/camel-bom-4.4.0.pom
> >
> > This PR fixes camel-bom
> > https://github.com/apache/camel/pull/13432
> >
> > Then we also need a fix for camel-spring-boot BOM as well
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.4.1 (LTS)
+1 (binding) On Mon, Mar 11, 2024 at 7:45 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.4.1, a new patch release with > 32 fixes and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354233=12311211 > > == Apache Camel 4.4.1 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1683/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1683/org/apache/camel/apache-camel/4.4.1/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.1 > > == Apache Camel Spring Boot 4.4.1 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1684/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.1 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Released BOM should have hardcoded camel version
Hi
https://issues.apache.org/jira/browse/CAMEL-20413
The BOM we release for both core and SB have
org.apache.camel
camel-api
${project.version}
But they should use the hardcoded release version, eg:
org.apache.camel
camel-api
4.4.0
If you look what we do now its wrong
https://repo1.maven.org/maven2/org/apache/camel/camel-bom/4.4.0/camel-bom-4.4.0.pom
This PR fixes camel-bom
https://github.com/apache/camel/pull/13432
Then we also need a fix for camel-spring-boot BOM as well
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.4.1 Release
Hi Gregor On Fri, Mar 8, 2024 at 5:44 PM Gregor Zurowski wrote: > I can take a look this weekend if that works for everyone. > > That is very good. The branches are ready. > On Mon, Mar 4, 2024 at 7:14 AM Claus Ibsen wrote: > > > > Hi > > > > I think it would be good to cut our first patch release for 4.4.x LTS > > branch this month. > > Better sooner than later. > > > > > > > > -- > > Claus Ibsen > > ----- > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: CAMEL-20518: Camel builds on Windows
Hi Yes it would be good to skip it on that win arm combination like kudu does. A PR is welcome. On Tue, Mar 5, 2024 at 6:55 PM Craig Ziesman wrote: > I get a different error running the build on Windows 11 via Parallels on an > M1 MacBook Pro. > > [ERROR] Failed to execute goal > org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile (default) on > project camel-salesforce: Unable to resolve artifact: Missing: > [ERROR] -- > [ERROR] 1) com.google.protobuf:protoc:exe:windows-aarch_64:3.25.3 > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [ERROR] > [ERROR] Then, install it using the command: > [ERROR] mvn install:install-file -DgroupId=com.google.protobuf > -DartifactId=protoc -Dversion=3.25.3 -Dclassifier=windows-aarch_64 > -Dpackaging=exe -Dfile=/path/to/file > [ERROR] > [ERROR] Alternatively, if you host your own repository you can deploy the > file there: > [ERROR] mvn deploy:deploy-file -DgroupId=com.google.protobuf > -DartifactId=protoc -Dversion=3.25.3 -Dclassifier=windows-aarch_64 > -Dpackaging=exe -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) org.apache.camel:camel-salesforce:jar:4.5.0-SNAPSHOT > [ERROR] 2) com.google.protobuf:protoc:exe:windows-aarch_64:3.25.3 > [ERROR] > [ERROR] -- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.apache.camel:camel-salesforce:jar:4.5.0-SNAPSHOT > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] central (https://repo1.maven.org/maven2/, releases=true, > snapshots=false), > [ERROR] apache.snapshots (https://repository.apache.org/snapshots, > releases=false, snapshots=true) > > It appears that there is no support for protocol buffers for Windows > running on ARM. Admittedly, that is probably a pretty small audience, but > it's still a problem with the build. I noticed that camel-kudo skips > building on Windows due to lack of library support. Perhaps the same should > be done here. > > > > On Tue, Mar 5, 2024 at 3:46 AM Otavio Rodolfo Piske > wrote: > > > Folks, > > > > Recently I noticed that Apache Camel is not building on Windows anymore. > > Most of the people in my network use Linux or macOS, so I'm sending this > > here to reach a larger audience. > > > > In case anyone has access to Windows, understands the platform and want > to > > take a look, here's the problem we are having: > > > > [ERROR] Failed to execute goal > > > org.apache.camel:camel-package-maven-plugin:4.5.0-SNAPSHOT:prepare-catalog > > (default) on project camel-catalog: Error preparing catalog: Error > reading > > json file: > > > > > D:\a\camel\camel\catalog\camel-catalog\..\..\components\camel-salesforce\camel-salesforce-component\target\classes\META-INF\org\apache\camel\component\salesforce\salesforce.json: > > Input length = 3 -> [Help 1] > > > > I created the following ticket for this problem: > > https://issues.apache.org/jira/browse/CAMEL-20518 > > > > Kind regards > > -- > > Otavio R. Piske > > http://orpiske.net > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Apache Camel 4.5 Release
Hi We have good progress on the next minor release. There is some work ongoing to simplify the maintenance of our generator code we use during building Camel. After this is complete, and maybe some other stuff, then it would be good to get a 4.5.0 release out to the community. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Apache Camel 4.4.1 Release
Hi I think it would be good to cut our first patch release for 4.4.x LTS branch this month. Better sooner than later. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release of Apache Camel Karavan 4.4.0
Hi Please help with this VOTE to ensure we have enough binding votes so karavan can be released, thanks. On Thu, Feb 29, 2024 at 3:44 AM Marat Gubaidullin < marat.gubaidul...@gmail.com> wrote: > Dear Camel Developers, > > This is a vote for the release of Apache Camel Karavan version 4.4.0. > > > Designer improvements: > 1. Support Variables in DSLs (From, To, Marshall, Unmarshall, etc) > 2. New DSLs for Variables (setVariable, removeVariable, convertVariableTo) > > 3. List of existing variables in DSL properties > 4. Navigation through `direct` and 'seda' between files > > 5. Accept to properties in `application.properties` in DSL placeholders > > 6. Create new property in `application.properties` from DSL placeholders > > 7. Simplified Expression > > 8. Component consumed/produced Headers in property UI > > > Web-application improvements: > 1. Configurable list of Components and Kamelets > 2. Configurable resource limits for projects in Docker > 3. Embedded cache instead of external > 4. Wizard to simply create beans (database, messaging, etc) > 5. Configurable Kubernetes Secrets -> Environment variables mapping for > build container > > 6. Support SSH Keys for Git Authentication > > Latest versions: > 1. Camel 4.4.0 > 5. Kamelets 4.4.0 > 7. Jkube 1.16.1 > 8. JBang v0.114.0 > > Source release package: > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.4.0/ > > Some files in the codebase have missing licence headers still. This is done > intentionally, because these files are code snippets/templates used to > generate user's code. > > VS Code Extension > https://github.com/apache/camel-karavan/releases/tag/4.4.0 > > We encourage all Camel contributors to participate in this release vote. > Your feedback and contributions play a crucial role in making Apache Camel > Karavan better with each release. > > Please cast your vote by replying to this email with your decision: > [ ] +1 Release > [ ] -1 Veto the release (provide specific comments) > > The voting period will remain open for 72 hours. > > Thank you for your continued support and dedication to the Apache Camel > project. > > My +1 is here > > Have a nice day, > Marat > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release of Apache Camel Karavan 4.4.0
+1 (binding) On Thu, Feb 29, 2024 at 3:44 AM Marat Gubaidullin < marat.gubaidul...@gmail.com> wrote: > Dear Camel Developers, > > This is a vote for the release of Apache Camel Karavan version 4.4.0. > > > Designer improvements: > 1. Support Variables in DSLs (From, To, Marshall, Unmarshall, etc) > 2. New DSLs for Variables (setVariable, removeVariable, convertVariableTo) > > 3. List of existing variables in DSL properties > 4. Navigation through `direct` and 'seda' between files > > 5. Accept to properties in `application.properties` in DSL placeholders > > 6. Create new property in `application.properties` from DSL placeholders > > 7. Simplified Expression > > 8. Component consumed/produced Headers in property UI > > > Web-application improvements: > 1. Configurable list of Components and Kamelets > 2. Configurable resource limits for projects in Docker > 3. Embedded cache instead of external > 4. Wizard to simply create beans (database, messaging, etc) > 5. Configurable Kubernetes Secrets -> Environment variables mapping for > build container > > 6. Support SSH Keys for Git Authentication > > Latest versions: > 1. Camel 4.4.0 > 5. Kamelets 4.4.0 > 7. Jkube 1.16.1 > 8. JBang v0.114.0 > > Source release package: > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.4.0/ > > Some files in the codebase have missing licence headers still. This is done > intentionally, because these files are code snippets/templates used to > generate user's code. > > VS Code Extension > https://github.com/apache/camel-karavan/releases/tag/4.4.0 > > We encourage all Camel contributors to participate in this release vote. > Your feedback and contributions play a crucial role in making Apache Camel > Karavan better with each release. > > Please cast your vote by replying to this email with your decision: > [ ] +1 Release > [ ] -1 Veto the release (provide specific comments) > > The voting period will remain open for 72 hours. > > Thank you for your continued support and dedication to the Apache Camel > project. > > My +1 is here > > Have a nice day, > Marat > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: REST DSL: add request param validation for already existing option "allowableValues"
Hi
You should write these kind of "how to do X with Camel" questions on the
user mailing list instead of dev (dev is for maintainer of Camel)
On Wed, Feb 28, 2024 at 8:08 PM Ja Li wrote:
> Hi devs,
>
> I just stumbled upon the REST DSL validation part:
> https://camel.apache.org/manual/rest-dsl.html#_client_request_validation
>
> 1) In case I use the "camel-restdsl-openapi-plugin" (Maven plugin) to
> generate REST DSL routes from an openapi specification, e.g.:
> ...
>
> testParam:
>
> name: testparam
>
> in: query
>
> required: true
>
> schema:
>
> type: integer
>
> format: int32
>
> enum: [0, 1, 2, 3, 4]
>
> ...
>
> it will generate the following Camel Route parameter for that:
>
> .param()
>
> .name("testparam")
>
> .type(RestParamType.query)
>
> .dataType("integer")
>
> .allowableValues("0,1,2,3,4")
>
> .required(true)
>
> .endParam()
>
>
> If I now enable the validation via
> "restConfiguration().component("jetty").clientRequestValidation(true);"
>
> I can still pass non-allowed values to the REST endpoint, e.g.
> localhost:8080/rest?testparam=6 and will get an HTTP 200.
>
>
> The documentation so far is only mentioning the "required" property (and
> this one is working) but as the ".allowableValues("0,1,2,3,4")" property
> obviously seems to already have been implemented I'm wondering why it is
> not validated then.
> My request is to add validation for this already existing option.
> It seems similar to the request years ago which has been answers by Claus:
> https://stackoverflow.com/a/50496017/5446400 and he points to the used
> HTTP
> component which should be responsible to actually fulfill the desired
> validation option defined in the route.
> I am currently using platform-http but also tried Jetty - it makes no
> difference.
>
>
> 2) Also can we maybe add support for the JSON property "allowEmptyValue"?
>
>
> 3) One last question which could also fit the user mailing list but as we
> are in the right context right now:
> Do you know any alternatives for validation of request parameters?
> Of course I could put them also into a json, send them to the REST endpoint
> and use a lot of validation annotations on its java data model (provided by
> libs as Jackson etc.) but we are using a HTTP GET endpoint and the RFC 7231
> standards do not allow GET requests with json bodies.
> So it seems as Camel doesn't provide full validation possibilities we have
> to manually check the incoming HTTP request parameter for validity?
>
> I am grateful for any tips!
>
> Kind regards
> Jacob
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: camel-restdsl-openapi-plugin 4.4.0 does not support openApi 3.1.0 specs: Unsupported document type: io.apicurio.datamodels.models.openapi.v31.OpenApi31DocumentImpl
Hi Yes 3.1 is not supported. You are welcome to create a JIRA and are also welcome to implement the code and send a PR On Mon, Feb 26, 2024 at 7:13 PM Ja Li wrote: > Hi there, > > I was trying to use the most up-to-date version of the following Maven > plugin to generate the REST routes and DTOs for a given openApi 3.1.0 spec: > org.apache.camel > camel-restdsl-openapi-plugin > 4.4.0 > > with default settings in the section and using the option: > "camel-restdsl-openapi:generate". > > Unfortunately it gave me this error: > [ERROR] Failed to execute goal > org.apache.camel:camel-restdsl-openapi-plugin:4.4.0:generate-with-dto > (generate-sources) on project openapi-test: Execution generate-sources of > goal org.apache.camel:camel-restdsl-openapi-plugin:4.4.0:generate-with-dto > failed: Unsupported document type: > io.apicurio.datamodels.models.openapi.v31.OpenApi31DocumentImpl > > (The Maven plugin camel-restdsl-openapi-plugin uses apicurio version 2.0.3 > (see: > > https://github.com/apache/camel/blob/main/tooling/openapi-rest-dsl-generator/pom.xml > => > > https://github.com/apache/camel/blob/e248d5cd78912c0b12f41565b44193f6d2db0008/parent/pom.xml > ) > but this apicurio version already contains/supports an openApi 3.1 > datamodel. It's just that this plugin seems not to be able to handle this > data model) > > So isn't the plugin compatible with openApi Spec 3.1.0? I can't see that > restriction from the plugin documentation here: > > https://github.com/apache/camel/blob/main/tooling/maven/camel-restdsl-openapi-plugin/src/main/docs/camel-restdsl-openapi-plugin.adoc > > > Thanks and kind regards > > Jacob > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Excessive use on the "git-websites" runners?
Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2 On Fri, 23 Feb 2024 at 12.34, Zoran Regvart wrote: > Hi Chris, Cameleers, > chiming in a bit late, apologies for that. I don't think we need to > build PR builds on Jenkins. We already build on GitHub Actions and > (when netlify CLI gets fixed) get previews there. I'd like to disable > building branches other than main on Jenkins. I think this should help > quite a bit with the queue depth on Jenkins. > > Thoughts? > Yes that is a good idea > zoran > > On Tue, Feb 20, 2024 at 11:13 AM Christofer Dutz > wrote: > > > > Hi all, > > > > Guess our release is out and the website was updated before that … so > guess I’m fine. > > And if you say that this is an unusual case, I also see no problems. > > From my perspective it just looked as if every PR was blocking a runner > and that would have been a problem, of course. > > > > If that’s not the case, I guess there’s no big problem. But limiting the > parallel usage of these runners is of course a good idea anyway. > > > > Chris > > > > Von: Claus Ibsen > > Datum: Montag, 19. Februar 2024 um 13:43 > > An: dev@camel.apache.org > > Betreff: Re: Excessive use on the "git-websites" runners? > > Hi > > > > Yeah ideally those CVEs should be in 1 merge to main - so they were > > released together. > > > > And frankly the website is rebuild from scratch each time, instead of > being > > able to update only parts of it. > > The CVEs only affect the security page + a new page per CVE. > > > > I stopped one of the builds, as there is a 2nd build in the queue to > > publish the last CVE. > > That should put your job ahead of ours. > > > > > > > > > > > > On Mon, Feb 19, 2024 at 1:37 PM Andrea Cosentino > wrote: > > > > > I don't think it would work on our website, but Zoran could have more > > > information about this. > > > > > > What we could do, it's maybe limit the number of builds on git-websites > > > nodes concurrently. > > > > > > Il giorno lun 19 feb 2024 alle ore 13:30 Christofer Dutz < > > > christofer.d...@c-ware.de> ha scritto: > > > > > > > Hi, > > > > > > > > as the PLC4X build also uses that, perhas what we did would be also > an > > > > option for you? > > > > We build the website on our own VM, but stash the built website … > then on > > > > the git-websites agent, we simply unstash what was built on our VM > and > > > > deploy that … this reduces the lock we have on shared infra to the > > > minimum > > > > … We’re also doing the same with deploying snapshots: We build on > our VM > > > > and use one of the ubuntu agents to deploy. > > > > > > > > Cause running a build on a PR, should probably not require staging of > > > > website changes … as soon as the PR is merged, then of course. > > > > > > > > Chris > > > > > > > > > > > > Von: Andrea Cosentino > > > > Datum: Montag, 19. Februar 2024 um 13:20 > > > > An: dev > > > > Betreff: Re: Excessive use on the "git-websites" runners? > > > > Usually there is not that much activities. There were 3 PRs related > to > > > cves > > > > and some related to the last release done during the weekend. So this > > > > should be just a temporary saturation. We don't have other way of > > > > publishing the website except using that mechanism. > > > > > > > > Il lun 19 feb 2024, 13:13 Christofer Dutz > ha > > > > scritto: > > > > > > > > > Hi all, > > > > > > > > > > I’m currently trying to finish up some stuff for the upcoming PLC4X > > > > > release. However am having problems because every time I want to > update > > > > our > > > > > website, I have to wait a long, long time, because all 3 runners > in the > > > > > “git-websites” class (websites1, websites2 and websites3) are > blocked > > > > with > > > > > really long running builds of Apache Camel. > > > > > > > > > > Most all have the tags associated with PRs … so I am asking > myself: Do > > > > > these builds have to be on git-websites? If not … it would be > > > appreciated > > > > > if you wouldn’t keep on blocking all runners. Of is currently > something > > > > out > > > > > of the ordinary going on? > > > > > > > > > > Chris > > > > > > > > > > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Zoran Regvart >
Re: [VOTE] Release Apache Camel Quarkus 3.8.0
+1 (binding) On Thu, Feb 22, 2024 at 9:22 AM Alexandre Gallice wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.8.0. > > Highlights: > > * Camel 4.4.0 > * Quarkus 3.8.0 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.7.0...3.8.0 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1682 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.8.0 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.8.0/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.8.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Remove old EOL releases from website docs
Hi Okay the old Camel K 1.12.x release is EOL and can be removed. This will allow the removal of EOL of Camel Quarkus and Kamelets and whatnot. On Mon, Feb 19, 2024 at 7:39 AM Claus Ibsen wrote: > CKC 4.0.x docs is now published, and removed the old 3.x docs. > > > On Sun, Feb 18, 2024 at 1:53 PM Claus Ibsen wrote: > >> Hi >> >> Okay we have 4.4 docs published. >> >> I am going to try to remove 3.14.x docs now. >> >> >> >> >> >> On Sun, Feb 18, 2024 at 11:11 AM Claus Ibsen >> wrote: >> >>> Hi >>> >>> We have some old releases like 3.14, and old Camel Q and K releases as >>> well. >>> After we have 4.4 LTS docs published. Then we can take a look at >>> removing old stuff. >>> >>> >>> >>> -- >>> Claus Ibsen >>> - >>> @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >>> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.4.0
+1 (binding) On Mon, Feb 19, 2024 at 3:14 PM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.4.0 > > This is the first release of camel-kamelets supporting LTS Camel 4.4.0 and > it contains many new Kamelets and a lot of fixes. > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.0 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1681 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.4.0 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.4.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Excessive use on the "git-websites" runners?
Hi Yeah ideally those CVEs should be in 1 merge to main - so they were released together. And frankly the website is rebuild from scratch each time, instead of being able to update only parts of it. The CVEs only affect the security page + a new page per CVE. I stopped one of the builds, as there is a 2nd build in the queue to publish the last CVE. That should put your job ahead of ours. On Mon, Feb 19, 2024 at 1:37 PM Andrea Cosentino wrote: > I don't think it would work on our website, but Zoran could have more > information about this. > > What we could do, it's maybe limit the number of builds on git-websites > nodes concurrently. > > Il giorno lun 19 feb 2024 alle ore 13:30 Christofer Dutz < > christofer.d...@c-ware.de> ha scritto: > > > Hi, > > > > as the PLC4X build also uses that, perhas what we did would be also an > > option for you? > > We build the website on our own VM, but stash the built website … then on > > the git-websites agent, we simply unstash what was built on our VM and > > deploy that … this reduces the lock we have on shared infra to the > minimum > > … We’re also doing the same with deploying snapshots: We build on our VM > > and use one of the ubuntu agents to deploy. > > > > Cause running a build on a PR, should probably not require staging of > > website changes … as soon as the PR is merged, then of course. > > > > Chris > > > > > > Von: Andrea Cosentino > > Datum: Montag, 19. Februar 2024 um 13:20 > > An: dev > > Betreff: Re: Excessive use on the "git-websites" runners? > > Usually there is not that much activities. There were 3 PRs related to > cves > > and some related to the last release done during the weekend. So this > > should be just a temporary saturation. We don't have other way of > > publishing the website except using that mechanism. > > > > Il lun 19 feb 2024, 13:13 Christofer Dutz ha > > scritto: > > > > > Hi all, > > > > > > I’m currently trying to finish up some stuff for the upcoming PLC4X > > > release. However am having problems because every time I want to update > > our > > > website, I have to wait a long, long time, because all 3 runners in the > > > “git-websites” class (websites1, websites2 and websites3) are blocked > > with > > > really long running builds of Apache Camel. > > > > > > Most all have the tags associated with PRs … so I am asking myself: Do > > > these builds have to be on git-websites? If not … it would be > appreciated > > > if you wouldn’t keep on blocking all runners. Of is currently something > > out > > > of the ordinary going on? > > > > > > Chris > > > > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Remove old EOL releases from website docs
CKC 4.0.x docs is now published, and removed the old 3.x docs. On Sun, Feb 18, 2024 at 1:53 PM Claus Ibsen wrote: > Hi > > Okay we have 4.4 docs published. > > I am going to try to remove 3.14.x docs now. > > > > > > On Sun, Feb 18, 2024 at 11:11 AM Claus Ibsen > wrote: > >> Hi >> >> We have some old releases like 3.14, and old Camel Q and K releases as >> well. >> After we have 4.4 LTS docs published. Then we can take a look at removing >> old stuff. >> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Remove old EOL releases from website docs
Hi Okay we have 4.4 docs published. I am going to try to remove 3.14.x docs now. On Sun, Feb 18, 2024 at 11:11 AM Claus Ibsen wrote: > Hi > > We have some old releases like 3.14, and old Camel Q and K releases as > well. > After we have 4.4 LTS docs published. Then we can take a look at removing > old stuff. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Remove old EOL releases from website docs
Hi We have some old releases like 3.14, and old Camel Q and K releases as well. After we have 4.4 LTS docs published. Then we can take a look at removing old stuff. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.4.0 (LTS)
Hi Gregor I wonder if you get time then it's appreciated to have this vote closed and releasing 4.4.0. On Mon, Feb 12, 2024 at 8:08 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.4.0, a new LTS release with > 152 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353989=12311211 > > == Apache Camel 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1679/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1679/org/apache/camel/apache-camel/4.4.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.0 > > == Apache Camel Spring Boot 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1680/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.4.0 (LTS)
Hi I created a draft blog about whats new in 4.4 https://github.com/apache/camel-website/pull/1139 Feedback is welcome and help to add more content is welcome on the PR. On Mon, Feb 12, 2024 at 8:08 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.4.0, a new LTS release with > 152 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353989=12311211 > > == Apache Camel 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1679/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1679/org/apache/camel/apache-camel/4.4.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.0 > > == Apache Camel Spring Boot 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1680/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.4.0 (LTS)
+1 (binding) Thanks for cutting the release so quickly. On Mon, Feb 12, 2024 at 8:08 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.4.0, a new LTS release with > 152 new features and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353989=12311211 > > == Apache Camel 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1679/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1679/org/apache/camel/apache-camel/4.4.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.0 > > == Apache Camel Spring Boot 4.4.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1680/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.4 LTS release this month
Hi Okay the branch is ready for cutting the release Gregor. On Mon, Feb 12, 2024 at 9:48 AM Andrea Cosentino wrote: > Thanks Gregor for your time. > > Il giorno lun 12 feb 2024 alle ore 09:47 Andrea Cosentino < > anco...@gmail.com> > ha scritto: > > > Morning, > > > > I just aligned the Google BOMs to the same versions matrix. > > > > I think we are good to go from my side. > > > > I want to add some documentation about sessionToken on AWS, but this can > > be done later too. > > > > So green light from me. > > > > Il giorno lun 12 feb 2024 alle ore 09:42 Claus Ibsen < > > claus.ib...@gmail.com> ha scritto: > > > >> Hi > >> > >> So just a heads up that we should get last minute details resolved > today, > >> so we can start the release process soon. > >> The CI server had a green build last day, and today there were just a > few > >> usual random test failures. > >> > >> Gregor we will get back to you later today with detail when you can > start > >> the release, thanks. > >> > >> On Wed, Feb 7, 2024 at 1:32 PM Claus Ibsen > wrote: > >> > >> > Hi Gregor > >> > > >> > Thanks for the notice. > >> > > >> > Otavio is working on the most important remaining issue about the > >> > throttler and will get this done by friday. > >> > The RAT check is passing and unit test are good. We only have a few > >> random > >> > test failures, and had a green test last weekend. > >> > > >> > > >> > > >> > On Tue, Feb 6, 2024 at 2:27 PM Gregor Zurowski < > >> gre...@list.zurowski.org> > >> > wrote: > >> > > >> >> I am available for cutting the release next week. > >> >> > >> >> Thanks, > >> >> Gregor > >> >> > >> >> On Tue, Feb 6, 2024 at 12:07 PM Claus Ibsen > >> >> wrote: > >> >> > > >> >> > Hi > >> >> > > >> >> > We should get ready for our next LTS release. > >> >> > > >> >> > There is a few outstanding work. > >> >> > > >> >> > Otavio is working on making the Throttle EIP work with both the old > >> and > >> >> new > >> >> > mode so its fully backwards compatible. > >> >> > > >> >> > I am doing a few minor things around languages and the new variable > >> >> feature > >> >> > coming in 4.4. > >> >> > > >> >> > The CI builds look good. We have only a few random test failures, > >> and a > >> >> few > >> >> > days ago the build was green. > >> >> > > >> >> > So let's push to get things done this week, so starting next week > we > >> >> would > >> >> > be ready for cutting the release. > >> >> > > >> >> > If you have anything that is important to get into the release, > then > >> >> bring > >> >> > this forward. > >> >> > > >> >> > Also you are welcome to move JIRA tickets from 4.4 to 4.5.0 if you > >> don't > >> >> > have time to work on this. > >> >> > > >> >> > > >> >> > Gregor, how does this look for you? > >> >> > > >> >> > > >> >> > -- > >> >> > Claus Ibsen > >> >> > - > >> >> > @davsclaus > >> >> > Camel in Action 2: https://www.manning.com/ibsen2 > >> >> > >> > > >> > > >> > -- > >> > Claus Ibsen > >> > - > >> > @davsclaus > >> > Camel in Action 2: https://www.manning.com/ibsen2 > >> > > >> > >> > >> -- > >> Claus Ibsen > >> - > >> @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.4 LTS release this month
Hi So just a heads up that we should get last minute details resolved today, so we can start the release process soon. The CI server had a green build last day, and today there were just a few usual random test failures. Gregor we will get back to you later today with detail when you can start the release, thanks. On Wed, Feb 7, 2024 at 1:32 PM Claus Ibsen wrote: > Hi Gregor > > Thanks for the notice. > > Otavio is working on the most important remaining issue about the > throttler and will get this done by friday. > The RAT check is passing and unit test are good. We only have a few random > test failures, and had a green test last weekend. > > > > On Tue, Feb 6, 2024 at 2:27 PM Gregor Zurowski > wrote: > >> I am available for cutting the release next week. >> >> Thanks, >> Gregor >> >> On Tue, Feb 6, 2024 at 12:07 PM Claus Ibsen >> wrote: >> > >> > Hi >> > >> > We should get ready for our next LTS release. >> > >> > There is a few outstanding work. >> > >> > Otavio is working on making the Throttle EIP work with both the old and >> new >> > mode so its fully backwards compatible. >> > >> > I am doing a few minor things around languages and the new variable >> feature >> > coming in 4.4. >> > >> > The CI builds look good. We have only a few random test failures, and a >> few >> > days ago the build was green. >> > >> > So let's push to get things done this week, so starting next week we >> would >> > be ready for cutting the release. >> > >> > If you have anything that is important to get into the release, then >> bring >> > this forward. >> > >> > Also you are welcome to move JIRA tickets from 4.4 to 4.5.0 if you don't >> > have time to work on this. >> > >> > >> > Gregor, how does this look for you? >> > >> > >> > -- >> > Claus Ibsen >> > - >> > @davsclaus >> > Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.4 LTS release this month
Hi Gregor Thanks for the notice. Otavio is working on the most important remaining issue about the throttler and will get this done by friday. The RAT check is passing and unit test are good. We only have a few random test failures, and had a green test last weekend. On Tue, Feb 6, 2024 at 2:27 PM Gregor Zurowski wrote: > I am available for cutting the release next week. > > Thanks, > Gregor > > On Tue, Feb 6, 2024 at 12:07 PM Claus Ibsen wrote: > > > > Hi > > > > We should get ready for our next LTS release. > > > > There is a few outstanding work. > > > > Otavio is working on making the Throttle EIP work with both the old and > new > > mode so its fully backwards compatible. > > > > I am doing a few minor things around languages and the new variable > feature > > coming in 4.4. > > > > The CI builds look good. We have only a few random test failures, and a > few > > days ago the build was green. > > > > So let's push to get things done this week, so starting next week we > would > > be ready for cutting the release. > > > > If you have anything that is important to get into the release, then > bring > > this forward. > > > > Also you are welcome to move JIRA tickets from 4.4 to 4.5.0 if you don't > > have time to work on this. > > > > > > Gregor, how does this look for you? > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel-kafka-connector 4.0.3
+1 (binding) On Tue, Feb 6, 2024 at 10:07 PM Andrea wrote: > Hello all, > > This is a vote to release Apache Camel-kafka-connector 4.0.3 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1678 > > Tag: > > https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-4.0.3 > > Update to camel 4.0.3 > > Please test this release candidate and cast your vote. > [ ] +1 Release the binary as Apache Camel-kafka-connector 4.0.3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Andrea. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Apache Camel 4.4 LTS release this month
Hi We should get ready for our next LTS release. There is a few outstanding work. Otavio is working on making the Throttle EIP work with both the old and new mode so its fully backwards compatible. I am doing a few minor things around languages and the new variable feature coming in 4.4. The CI builds look good. We have only a few random test failures, and a few days ago the build was green. So let's push to get things done this week, so starting next week we would be ready for cutting the release. If you have anything that is important to get into the release, then bring this forward. Also you are welcome to move JIRA tickets from 4.4 to 4.5.0 if you don't have time to work on this. Gregor, how does this look for you? -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.0.4
+1 (binding) On Sun, Jan 28, 2024 at 8:47 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.0.4, a new patch release with > 23 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353858=12311211 > > == Apache Camel 4.0.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1676/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1676/org/apache/camel/camel/4.0.4/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.4 > > == Apache Camel Spring Boot 4.0.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1677/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1677/org/apache/camel/springboot/spring-boot/4.0.4/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.4 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.4 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 3.22.1 (LTS)
+1 (binding) On Fri, Jan 26, 2024 at 5:51 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.22.1, a new patch release > with 8 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354118=12311211 > > == Apache Camel 3.22.1 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1673/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1673/org/apache/camel/apache-camel/3.22.1/ > > Tag: https://github.com/apache/camel/releases/tag/camel-3.22.1 > > == Apache Camel Spring Boot 3.22.1 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1674/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.22.1 > > == Apache Camel Karaf 3.22.1 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1675/ > > Tag: https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.22.1 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.22.1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Quarkus 3.7.0
+1 (binding) On Thu, Jan 25, 2024 at 5:23 PM James Netherton wrote: > Hi, > > This is a vote to release Apache Camel Quarkus 3.7.0. > > Highlights: > > * Camel 4.3.0 > * Quarkus 3.7.0 > > All commits: > > https://github.com/apache/camel-quarkus/compare/3.6.0...3.7.0 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1672 > > Tag: > > https://github.com/apache/camel-quarkus/releases/tag/3.7.0 > > Source release package + SBOM: > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.7.0/ > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.7.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Should *IT tests be run with failsafe instead of surefire?
Hi Yes those tests should ideally be run in the verify phase. Also as someone whom does not have docker running always, I would like for those docker based tests to graceful be disabled and the build can skip those tests and continue building. It happens for some components, other fails with "docker environment not found" error. On Wed, Jan 24, 2024 at 9:22 PM Craig Ziesman wrote: > I've been working with the Camel build and investigating test failures. > > There are many tests that use TestContainers and Docker in *IT.java classes > that are currently being run by the surefire plugin. In my opinion, these > tests ought to be run by failsafe, as they seem to meet the definition of > integration tests, not unit tests, and should not cause the whole build to > fail if any of them fail. > > I would be happy to generate a PR to move these tests to surefire if there > is no objection from the team. > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 3.21.4 (LTS)
+1 (binding) On Thu, Jan 25, 2024 at 10:20 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.21.4, a new patch release > with 9 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354021=12311211 > > == Apache Camel 3.21.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1669/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1669/org/apache/camel/apache-camel/3.21.4/ > > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.4 > > == Apache Camel Spring Boot 3.21.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1670/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.4 > > == Apache Camel Karaf 3.21.4 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1671/ > > Tag: https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.4 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.21.4 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.0.3
+1 (binding) On Wed, Jan 17, 2024 at 9:32 AM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.0.3 > > This release will support the 4.0.3 release of Apache Camel. The aim of the > release is to have a catalog to use in generating camel-kafka-connector > 4.0.3 release. > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.3 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1668 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.0.3 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Camel K 2.2.0 release *second attempt
+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 > <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 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Adding JMX reporting and control to dynamic router eip component
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 filte
Apache Camel 4.4 LTS release in February 2024
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
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
urn 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 Map.copyOf(filterStatisticsMap);
> }
>
> @Override
> public void start() {
> // no-op
> }
>
> @Override
> public void stop() {
> // no-op
> }
> }
>
> I want to write a test that verifies that camel is registering these. I
> have added camel-management to my pom in the "test" scope. I originally
> tried to use a test annotated with @CamelSpringTest, but I could not it to
> work, and when I tried to get the ManagementAgent, it was always null. So
> I switched to a normal test that extends CamelTestSupport, and now I can at
> least get the agent and the MBeanServer. Here is my test class:
>
> class DynamicRouterManagementIT extends CamelTestSupport {
>
> @Override
> protected boolean useJmx() {
> return true;
> }
>
> @Test
> void testExpectedMbeansExist() throws MalformedObjectNameException {
> MBeanServer mBeanServer =
> context.getManagementStrategy().getManagementAgent().getMBeanServer();
> String names = mBeanServer.queryNames(null, null).stream()
> .map(ObjectName::getCanonicalName)
> .filter(name -> name.contains("ynamic"))
> .collect(Collectors.joining("\n"));
> System.err.println("MBean names:\n" + names);
> }
>
> @Override
> protected RoutesBuilder createRouteBuilder() {
> return new RouteBuilder() {
> @Override
> public void configure() {
>
> from("direct:subscribe").to("dynamic-router-control:subscribe");
> from("direct:command").to("dynamic-router:test");
> }
> };
> }
> }
>
> The output does not show either of the two @ManagedResource classes. Here
> is the output:
>
> MBean names:
> >
> >
> org.apache.camel:context=camel-1,name="dynamic-router-control",type=components
> > org.apache.camel:context=camel-1,name="dynamic-router",type=components
> >
> >
> org.apache.camel:context=camel-1,name="dynamic-router-control://subscribe",type=endpoints
> >
> >
> org.apache.camel:context=camel-1,name=DynamicRouterProducer(0x511505e7),type=producers
> >
> >
> org.apache.camel:context=camel-1,name=DynamicRouterControlProducer(0x70abf9b0),type=producers
> >
> >
> org.apache.camel:context=camel-1,name="dynamic-router://test",type=endpoints
>
>
> Why don't I see the MBeans that I expect for the classes that I included
> above?
>
> Thanks,
> Steve
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Introducing variables to Camel 4.4
On Tue, Jan 2, 2024 at 3:26 PM Alexandre Gallice
wrote:
> Hi Claus,
>
> Looks interesting. New year, new idea :)
>
> I wonder what is the difference between exchange property and variable.
> Don't they have the same scope and mutability ?
>
>
exchange properties is a mixed bag of internal stuff and yes users can also
store their own stuff there.
But then you end up with user stuff and internal camel stuff. Also exchange
properties are private per exchange only.
Variables = 100% end user.
And you can have different scopes / repositories so you can share
variables, or persist them or whatever.
Also a variable is a more common concept for users as it's something every
programming language has.
Exchange properties can be mistaken for those "properties" you configure on
endpoints, components, and in application.properties, and when using
property placeholders {{xxx}}.
In fact they were called properties in Camel 1.x/2.x and renamed to
exchange properties to better say that these are properties on an exchange,
and not any of
> Cheers,
> Alex
>
> On Sun, Dec 31, 2023 at 1:16 PM Claus Ibsen wrote:
>
> > Hi
> >
> > JIRA
> > https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-19749
> >
> > We are working on adding support for variables to Camel.
> >
> > See more in the docs at
> >
> >
> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/variables.adoc
> >
> > And examples for Spring Boot and Main / JBang
> > https://github.com/apache/camel-spring-boot-examples/tree/main/variables
> >
> https://github.com/apache/camel-kamelets-examples/tree/main/jbang/variables
> >
> > There is more work coming, but this is the initial and basics of
> variables.
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release of Apache Camel Karavan 4.3.0
Hi Happy new year. It would be good to get some more votes for this release, thanks. On Thu, Dec 28, 2023 at 5:06 PM Marat Gubaidullin < marat.gubaidul...@gmail.com> wrote: > Dear Camel Developers, > > This is a vote for the release of Apache Camel Karavan version 4.3.0. > > What's new in this version: > > Designer improvements: > 1. Less verbose UI > 2. Users can convert Filter DSL to Choice > 3. Users can convert SetHeader to SetBody > 4. Users can DSL element with steps to Route > 5. Configurable Auto Startup in a route using Env variable > 6. Header information for Components in Knowledgebase > > Web-application improvements: > 1. Configurable network for Karavan in Docker > 2. Configurable Service Account for DevMode container in Kubernetes > 3. Users can add README.md with project description > 4. Users can pull project from Git repository > 5. Configurable OIDC realm and client ID > 6. When Karavan authorized in OIDC, Git commit includes author name and > email from authorized user > > Latest versions: > - Camel 4.3.0 > - Kamelets 4.3.0 > - Jkube 1.15.0 > - JBang v0.114.0 > > Source release package: > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.3.0/ > > Some files in the codebase have missing licence headers still. This is done > intentionally, because these files are code snippets/templates used to > generate user's code. > > VS Code Extension > https://github.com/apache/camel-karavan/releases/tag/4.3.0 > > We encourage all Camel contributors to participate in this release vote. > Your feedback and contributions play a crucial role in making Apache Camel > Karavan better with each release. > > Please cast your vote by replying to this email with your decision: > [ ] +1 Release > [ ] -1 Veto the release (provide specific comments) > > The voting period will remain open for 72 hours. > > Thank you for your continued support and dedication to the Apache Camel > project. > > My +1 is here > > Have a nice day, > Marat > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
[HEADS UP] - Introducing variables to Camel 4.4
Hi JIRA https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-19749 We are working on adding support for variables to Camel. See more in the docs at https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/variables.adoc And examples for Spring Boot and Main / JBang https://github.com/apache/camel-spring-boot-examples/tree/main/variables https://github.com/apache/camel-kamelets-examples/tree/main/jbang/variables There is more work coming, but this is the initial and basics of variables. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release of Apache Camel Karavan 4.3.0
+1 (binding) On Thu, Dec 28, 2023 at 5:06 PM Marat Gubaidullin < marat.gubaidul...@gmail.com> wrote: > Dear Camel Developers, > > This is a vote for the release of Apache Camel Karavan version 4.3.0. > > What's new in this version: > > Designer improvements: > 1. Less verbose UI > 2. Users can convert Filter DSL to Choice > 3. Users can convert SetHeader to SetBody > 4. Users can DSL element with steps to Route > 5. Configurable Auto Startup in a route using Env variable > 6. Header information for Components in Knowledgebase > > Web-application improvements: > 1. Configurable network for Karavan in Docker > 2. Configurable Service Account for DevMode container in Kubernetes > 3. Users can add README.md with project description > 4. Users can pull project from Git repository > 5. Configurable OIDC realm and client ID > 6. When Karavan authorized in OIDC, Git commit includes author name and > email from authorized user > > Latest versions: > - Camel 4.3.0 > - Kamelets 4.3.0 > - Jkube 1.15.0 > - JBang v0.114.0 > > Source release package: > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.3.0/ > > Some files in the codebase have missing licence headers still. This is done > intentionally, because these files are code snippets/templates used to > generate user's code. > > VS Code Extension > https://github.com/apache/camel-karavan/releases/tag/4.3.0 > > We encourage all Camel contributors to participate in this release vote. > Your feedback and contributions play a crucial role in making Apache Camel > Karavan better with each release. > > Please cast your vote by replying to this email with your decision: > [ ] +1 Release > [ ] -1 Veto the release (provide specific comments) > > The voting period will remain open for 72 hours. > > Thank you for your continued support and dedication to the Apache Camel > project. > > My +1 is here > > Have a nice day, > Marat > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 3.22.0 (LTS)
+1 (binding) On Wed, Dec 20, 2023 at 1:35 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.22.0, a new LTS release with > 100 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353350=12311211 > > == Apache Camel 3.22.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1661/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1661/org/apache/camel/apache-camel/3.22.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-3.22.0 > > == Apache Camel Spring Boot 3.22.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1663/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.22.0 > > == Apache Camel Karaf 3.22.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1664/ > > Tag: https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.22.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.22.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel K 2.2.0
+1 (binding) On Tue, Dec 19, 2023 at 6:35 PM 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.6.0 (based on > Camel 4.2.0). > > 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-1662/ > > Staging container image repository: > AMD64 architecture: > > https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-2985140def53d41ac86409abc97bb21e7bbf044a63eb541fdf55a5b6d1e5a526?context=explore > ARM64 > <https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-2985140def53d41ac86409abc97bb21e7bbf044a63eb541fdf55a5b6d1e5a526?context=exploreARM64> > architecture (preview only): > > https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-726a52b9e5f31ab318082a68284f7400a44909fd8a8bd9e8a887175346db6d59?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: Apache Camel 3.22.0 Release (last 3.x)
Hi
Ah okay the 3.22 is Java 11 as minimum version, so that javadoc plugin
should be bumped to 11 instead of 8.
On Tue, Dec 19, 2023 at 11:43 AM Andrea Cosentino wrote:
> Looks good to me.
>
> Thanks Gregor.
>
> Il giorno mar 19 dic 2023 alle ore 11:42 Gregor Zurowski <
> gre...@list.zurowski.org> ha scritto:
>
> > I am having the following issue when building the 3.x branch:
> >
> > ```
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:jar
> > (attach-javadocs) on project camel-api: MavenReportException: Error
> > while generating Javadoc:
> > [ERROR] Exit code: 1 -
> >
> >
> /git/camel/core/camel-api/src/main/java/org/apache/camel/support/jsse/KeyStoreParameters.java:196:
> > error: variables in try-with-resources are not supported in -source 8
> > [ERROR] try (is) {
> > [ERROR]^
> > [ERROR] (use -source 9 or higher to enable variables in
> > try-with-resources)
> > ```
> >
> > It is essentially about the use of try-with-resources here:
> >
> >
> https://github.com/apache/camel/blob/a4c5c22b3a630a5d080d293db02655962d6732ca/core/camel-api/src/main/java/org/apache/camel/support/jsse/KeyStoreParameters.java#L196
> > :
> >
> > It was introduced with this PR:
> > https://github.com/apache/camel/pull/11317/files
> >
> > Note that the maven-java-doc plugin is set to Java 8 on the 3.x
> > branch, although I am not sure how this plays into the problem.
> >
> > I have addressed it as follows:
> >
> >
> https://github.com/apache/camel/commit/8803f11b30953da9bf46387e9fd98afa072fa06e
> >
> > Please let me know if you have any concerns.
> >
> > Thanks in advance,
> > Gregor
> >
> >
> > On Wed, Dec 13, 2023 at 9:06 AM Andrea Cosentino
> > wrote:
> > >
> > > +1, I would like to add the SBOM also to the branch, so we can publish
> > it,
> > > but we can do that by hand too.
> > >
> > >
> > >
> > > Il giorno mer 13 dic 2023 alle ore 08:46 Claus Ibsen <
> > claus.ib...@gmail.com>
> > > ha scritto:
> > >
> > > > Hi
> > > >
> > > > Okay so camel-3.x branches are ready for cutting 3.22.0 release.
> > > >
> > > >
> > > > On Tue, Dec 12, 2023 at 5:10 PM Claus Ibsen
> > wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > We have one last release in 3.x which is the 3.22.0 release.
> > > > >
> > > > > This is a smaller 3.x release and is the last planned for 3.x.
> Users
> > on
> > > > > 3.x should consider upgrading to v4, and start new development on
> v4
> > if
> > > > > possible.
> > > > >
> > > > > There are no more planned work for 3.22.0, so we can do a sanity
> > check on
> > > > > the branches, and then if Gregor still has time then we can
> possible
> > have
> > > > > it released later this year.
> > > > >
> > > > > The plan is for 3.22.0 to be LTS until end of 2024. However we do
> not
> > > > > focus on 3.x anymore and this release will not come with many patch
> > > > > releases. We only fix critical CVEs reported in Camel source code,
> > and
> > > > > other very important bug fixes.
> > > > >
> > > > > When we have the 3.22.0 release, then we should do a blog post
> about
> > the
> > > > > "end of 3.x"
> > > > >
> > > > >
> > > > > --
> > > > > Claus Ibsen
> > > > > -
> > > > > @davsclaus
> > > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> >
>
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel Kamelets 4.3.0
+1 (binding) On Tue, Dec 19, 2023 at 9:36 AM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.3.0 > > This release will support the 4.3.0 release of Apache Camel. > > More info at: > https://github.com/apache/camel-kamelets/blob/main/CHANGELOG.md > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.3.0 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1660 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.3.0 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.3.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4.3 whats new blog post
Andrea you may want to help add a bit about SBom which we now publish for our releases. Otavio maybe you have some stuff improved in the core that is worth to mention. On Thu, Dec 14, 2023 at 1:28 PM Claus Ibsen wrote: > Hi > > I created a quick draft for the blog post. We need to flesh out more > content, and I added TODOs. > > Feel free to update the PR > https://github.com/apache/camel-website/pull/1107 > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Camel 4.3 whats new blog post
Hi I created a quick draft for the blog post. We need to flesh out more content, and I added TODOs. Feel free to update the PR https://github.com/apache/camel-website/pull/1107 -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3.22.0 Release (last 3.x)
Hi Okay so camel-3.x branches are ready for cutting 3.22.0 release. On Tue, Dec 12, 2023 at 5:10 PM Claus Ibsen wrote: > Hi > > We have one last release in 3.x which is the 3.22.0 release. > > This is a smaller 3.x release and is the last planned for 3.x. Users on > 3.x should consider upgrading to v4, and start new development on v4 if > possible. > > There are no more planned work for 3.22.0, so we can do a sanity check on > the branches, and then if Gregor still has time then we can possible have > it released later this year. > > The plan is for 3.22.0 to be LTS until end of 2024. However we do not > focus on 3.x anymore and this release will not come with many patch > releases. We only fix critical CVEs reported in Camel source code, and > other very important bug fixes. > > When we have the 3.22.0 release, then we should do a blog post about the > "end of 3.x" > > > -- > Claus Ibsen > ----- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Apache Camel 3.22.0 Release (last 3.x)
Hi We have one last release in 3.x which is the 3.22.0 release. This is a smaller 3.x release and is the last planned for 3.x. Users on 3.x should consider upgrading to v4, and start new development on v4 if possible. There are no more planned work for 3.22.0, so we can do a sanity check on the branches, and then if Gregor still has time then we can possible have it released later this year. The plan is for 3.22.0 to be LTS until end of 2024. However we do not focus on 3.x anymore and this release will not come with many patch releases. We only fix critical CVEs reported in Camel source code, and other very important bug fixes. When we have the 3.22.0 release, then we should do a blog post about the "end of 3.x" -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Apache Camel 4.3.0
+1 (binding) On Tue, Dec 12, 2023 at 9:24 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 4.3.0, a new release with 108 > new features and improvements. It is the first Camel release that was > built with Java 21. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353751=12311211 > > == Apache Camel 4.3.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1658/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1658/org/apache/camel/apache-camel/4.3.0/ > > Tag: https://github.com/apache/camel/releases/tag/camel-4.3.0 > > == Apache Camel Spring Boot 4.3.0 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1659/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.3.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.3.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Camel K Runtime 3.6.0 and 3.2.3
+1 (binding) On Mon, Dec 11, 2023 at 4:13 PM Pasquale Congiusti < pasquale.congiu...@gmail.com> wrote: > Hello, > > This is a combined vote to release Camel K Runtime 3.6.0 and 3.2.3. This > release will provide the runtime for to Camel Quarkus 3.6.0 (based on Camel > 4.2.0) and 3.2.3 respectively. > > # Camel K runtime version 3.2.3 > > Camel K Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.2.3/ > > Camel K Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1656 > > Camel K Runtime Tag: > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.2.3 > > It's possible test the staging artifacts by installing the latest Camel K > CLI (kamel) with the staging repository and run any Integration with the > new runtime: > > - > kamel install --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1656 > ... > > kamel run Test.java -t camel.runtime-version=3.2.3 > - > > Please test these release candidates and cast your vote. > > # Camel K runtime version 3.6.0 > > Camel K Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.6.0/ > > Camel K Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1657 > > Camel K Runtime Tag: > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.6.0 > > It's possible test the staging artifacts by installing the latest Camel K > CLI (kamel) with the staging repository and run any Integration with the > new runtime: > > - > kamel install --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1657 > ... > > kamel run Test.java -t camel.runtime-version=3.6.0 > - > > Please test these release candidates and cast your vote. > > [ ] +1 Release Apache Camel K Runtime 3.6.0 and 3.2.3 > [ ] -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 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.3.0 Release in December
Hi Gregor Okay the fix has been merged to main branch. The release can continue On Mon, Dec 11, 2023 at 2:25 PM Claus Ibsen wrote: > Hi > > Gregor I have a PR on the way that fixes a bug in an EIP that we need to > get into the release. > https://github.com/apache/camel/pull/12399 > > The PR just needs to be tested on CI and when its merged you can rebuild > from last main branch. > > > > On Mon, Dec 11, 2023 at 2:24 PM Andrea Cosentino > wrote: > >> Yes, we should disable them as default and maybe add a TODO later. >> >> Il giorno lun 11 dic 2023 alle ore 14:22 Gregor Zurowski < >> gre...@list.zurowski.org> ha scritto: >> >> > I am looking at the `main` branch and I am running into the same issue >> > with camel-package-maven-plugin as with previous 4.x releases: >> > >> > ``` >> > [ERROR] Plugin >> org.apache.camel:camel-package-maven-plugin:4.3.0-SNAPSHOT >> > or one of its dependencies could not be resolved: The following >> > artifacts could not be resolved: >> > org.apache.camel:camel-package-maven-plugin:jar:4.3.0-SNAPSHOT >> > (absent): Could not find artifact >> > org.apache.camel:camel-package-maven-plugin:jar:4.3.0-SNAPSHOT -> >> > [Help 1] >> > ``` >> > >> > Should I disabled the integration tests? >> > >> > Thanks, >> > Gregor >> > >> > On Mon, Dec 11, 2023 at 12:51 PM Claus Ibsen >> > wrote: >> > > >> > > Hi Gregor >> > > >> > > If you are reading this then the main branch is ready for 4.3.0 >> release. >> > > Remember to use JDK21 to build this release. >> > > >> > > On Mon, Dec 11, 2023 at 9:57 AM Claus Ibsen >> > wrote: >> > > >> > > > Hi >> > > > >> > > > Okay so 4.3.0 is starting to shape up and will be ready early this >> week >> > > > for cutting the release. >> > > > >> > > > On Wed, Dec 6, 2023 at 1:00 PM Claus Ibsen >> > wrote: >> > > > >> > > >> Hi Gregor >> > > >> >> > > >> Okay so both 3.20.x and 3.21.x branches are ready for cutting patch >> > > >> releases. >> > > >> >> > > >> >> > > >> On Wed, Dec 6, 2023 at 12:02 PM Claus Ibsen > > >> > > >> wrote: >> > > >> >> > > >>> Hi Gregor >> > > >>> >> > > >>> Okay 3.20.x branch is ready for cutting the final release. It >> will be >> > > >>> EOL by end of this year. >> > > >>> I am checking 3.21.x right now. >> > > >>> >> > > >>> On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen < >> claus.ib...@gmail.com> >> > > >>> wrote: >> > > >>> >> > > >>>> >> > > >>>> >> > > >>>> On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski < >> > > >>>> gre...@list.zurowski.org> wrote: >> > > >>>> >> > > >>>>> Hi Claus, >> > > >>>>> >> > > >>>>> No worries, I can pick up the 4.3.0 release either this weekend >> or >> > mid >> > > >>>>> next week. >> > > >>>>> >> > > >>>>> Let's also align on when to start cutting the patch and 3.22 >> > releases. >> > > >>>>> Can I go ahead and start the final 3.20.9 release immediately, >> or >> > are >> > > >>>>> we still waiting on any last patches? >> > > >>>>> >> > > >>>>> >> > > >>>> I am doing some sanity check on 3.20.x right now. I had a power >> > > >>>> black-out for 1h so I had to do real hard work by showing snow. >> > > >>>> But power is back, so I will check the 3.20.x and 3.21.x branches >> > and >> > > >>>> then let you know later so we can start cutting patch releases. >> > > >>>> And then do 4.3 next week when the elastisearch component is >> ready. >> > > >>>> >> > > >>>> >> > > >>>> >> > > >>>>> Thanks, >> > > >>>>> Gregor >> > > >
Re: Apache Camel 4.3.0 Release in December
Hi Gregor I have a PR on the way that fixes a bug in an EIP that we need to get into the release. https://github.com/apache/camel/pull/12399 The PR just needs to be tested on CI and when its merged you can rebuild from last main branch. On Mon, Dec 11, 2023 at 2:24 PM Andrea Cosentino wrote: > Yes, we should disable them as default and maybe add a TODO later. > > Il giorno lun 11 dic 2023 alle ore 14:22 Gregor Zurowski < > gre...@list.zurowski.org> ha scritto: > > > I am looking at the `main` branch and I am running into the same issue > > with camel-package-maven-plugin as with previous 4.x releases: > > > > ``` > > [ERROR] Plugin org.apache.camel:camel-package-maven-plugin:4.3.0-SNAPSHOT > > or one of its dependencies could not be resolved: The following > > artifacts could not be resolved: > > org.apache.camel:camel-package-maven-plugin:jar:4.3.0-SNAPSHOT > > (absent): Could not find artifact > > org.apache.camel:camel-package-maven-plugin:jar:4.3.0-SNAPSHOT -> > > [Help 1] > > ``` > > > > Should I disabled the integration tests? > > > > Thanks, > > Gregor > > > > On Mon, Dec 11, 2023 at 12:51 PM Claus Ibsen > > wrote: > > > > > > Hi Gregor > > > > > > If you are reading this then the main branch is ready for 4.3.0 > release. > > > Remember to use JDK21 to build this release. > > > > > > On Mon, Dec 11, 2023 at 9:57 AM Claus Ibsen > > wrote: > > > > > > > Hi > > > > > > > > Okay so 4.3.0 is starting to shape up and will be ready early this > week > > > > for cutting the release. > > > > > > > > On Wed, Dec 6, 2023 at 1:00 PM Claus Ibsen > > wrote: > > > > > > > >> Hi Gregor > > > >> > > > >> Okay so both 3.20.x and 3.21.x branches are ready for cutting patch > > > >> releases. > > > >> > > > >> > > > >> On Wed, Dec 6, 2023 at 12:02 PM Claus Ibsen > > > >> wrote: > > > >> > > > >>> Hi Gregor > > > >>> > > > >>> Okay 3.20.x branch is ready for cutting the final release. It will > be > > > >>> EOL by end of this year. > > > >>> I am checking 3.21.x right now. > > > >>> > > > >>> On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen > > > > >>> wrote: > > > >>> > > > >>>> > > > >>>> > > > >>>> On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski < > > > >>>> gre...@list.zurowski.org> wrote: > > > >>>> > > > >>>>> Hi Claus, > > > >>>>> > > > >>>>> No worries, I can pick up the 4.3.0 release either this weekend > or > > mid > > > >>>>> next week. > > > >>>>> > > > >>>>> Let's also align on when to start cutting the patch and 3.22 > > releases. > > > >>>>> Can I go ahead and start the final 3.20.9 release immediately, or > > are > > > >>>>> we still waiting on any last patches? > > > >>>>> > > > >>>>> > > > >>>> I am doing some sanity check on 3.20.x right now. I had a power > > > >>>> black-out for 1h so I had to do real hard work by showing snow. > > > >>>> But power is back, so I will check the 3.20.x and 3.21.x branches > > and > > > >>>> then let you know later so we can start cutting patch releases. > > > >>>> And then do 4.3 next week when the elastisearch component is > ready. > > > >>>> > > > >>>> > > > >>>> > > > >>>>> Thanks, > > > >>>>> Gregor > > > >>>>> > > > >>>>> On Wed, Dec 6, 2023 at 9:57 AM Claus Ibsen < > claus.ib...@gmail.com> > > > >>>>> wrote: > > > >>>>> > > > > >>>>> > Hi Gregor > > > >>>>> > > > > >>>>> > What does your schedule look like? Would you have best for > > building > > > >>>>> the > > > >>>>> > starting on friday, or should we push this out to mid of next > > week? > > > >>>>>
Re: Apache Camel 4.3.0 Release in December
Hi Gregor If you are reading this then the main branch is ready for 4.3.0 release. Remember to use JDK21 to build this release. On Mon, Dec 11, 2023 at 9:57 AM Claus Ibsen wrote: > Hi > > Okay so 4.3.0 is starting to shape up and will be ready early this week > for cutting the release. > > On Wed, Dec 6, 2023 at 1:00 PM Claus Ibsen wrote: > >> Hi Gregor >> >> Okay so both 3.20.x and 3.21.x branches are ready for cutting patch >> releases. >> >> >> On Wed, Dec 6, 2023 at 12:02 PM Claus Ibsen >> wrote: >> >>> Hi Gregor >>> >>> Okay 3.20.x branch is ready for cutting the final release. It will be >>> EOL by end of this year. >>> I am checking 3.21.x right now. >>> >>> On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen >>> wrote: >>> >>>> >>>> >>>> On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski < >>>> gre...@list.zurowski.org> wrote: >>>> >>>>> Hi Claus, >>>>> >>>>> No worries, I can pick up the 4.3.0 release either this weekend or mid >>>>> next week. >>>>> >>>>> Let's also align on when to start cutting the patch and 3.22 releases. >>>>> Can I go ahead and start the final 3.20.9 release immediately, or are >>>>> we still waiting on any last patches? >>>>> >>>>> >>>> I am doing some sanity check on 3.20.x right now. I had a power >>>> black-out for 1h so I had to do real hard work by showing snow. >>>> But power is back, so I will check the 3.20.x and 3.21.x branches and >>>> then let you know later so we can start cutting patch releases. >>>> And then do 4.3 next week when the elastisearch component is ready. >>>> >>>> >>>> >>>>> Thanks, >>>>> Gregor >>>>> >>>>> On Wed, Dec 6, 2023 at 9:57 AM Claus Ibsen >>>>> wrote: >>>>> > >>>>> > Hi Gregor >>>>> > >>>>> > What does your schedule look like? Would you have best for building >>>>> the >>>>> > starting on friday, or should we push this out to mid of next week? >>>>> > There is a potential new camel-elasticsearch component in the works, >>>>> but >>>>> > it's not ready yet, but we may get it ready for mid next week. >>>>> > However as building and release is a burden on you then we want to >>>>> > accommodate what works best for you. >>>>> > >>>>> > Also it would be good to do final patch releases for 3.20.x as it >>>>> goes EOL >>>>> > by end of year. >>>>> > And also the 3.22.0 release, and maybe a 3.21.x patch release too. >>>>> > So there are plenty of old releases as well. >>>>> > >>>>> > >>>>> > >>>>> > On Tue, Dec 5, 2023 at 2:42 PM Claus Ibsen >>>>> wrote: >>>>> > >>>>> > > Hi >>>>> > > >>>>> > > Okay so we have upgraded to Jetty 12, and the core project seems >>>>> okay. >>>>> > > Federico is checking Camel Spring Boot and reports back when its >>>>> okay. >>>>> > > >>>>> > > There is also the Virtual Threads experiment that Nicolas work on. >>>>> > > If merged to main, then this would require for you to build the >>>>> release >>>>> > > with Java 21. >>>>> > > But the generated JARs will work on JDK17 as well. >>>>> > > https://github.com/apache/camel/pull/12292 >>>>> > > >>>>> > > >>>>> > > If all goes well we may be ready by friday. We will keep you >>>>> posted here. >>>>> > > >>>>> > > >>>>> > > On Sat, Dec 2, 2023 at 7:43 AM Claus Ibsen >>>>> wrote: >>>>> > > >>>>> > >> Hi Gregor >>>>> > >> >>>>> > >> Thanks. >>>>> > >> >>>>> > >> Let's see later next week where we are. There is still some work >>>>> to do >>>>> > >> for the SB 3.2 upgrade. >>>>> > >> >>>>> > >> >>>>> >
Re: [VOTE] Release Apache Camel 3.21.3 (LTS)
+1 (binding) On Mon, Dec 11, 2023 at 12:22 PM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.21.3, a new patch release > with 14 improvements and fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353747=12311211 > > == Apache Camel 3.21.3 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1653/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1653/org/apache/camel/apache-camel/3.21.3/ > > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.3 > > == Apache Camel Spring Boot 3.21.3 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1654/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.3 > > == Apache Camel Karaf 3.21.3 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1655/ > > Tag: https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.3 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.21.3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.3.0 Release in December
Hi Okay so 4.3.0 is starting to shape up and will be ready early this week for cutting the release. On Wed, Dec 6, 2023 at 1:00 PM Claus Ibsen wrote: > Hi Gregor > > Okay so both 3.20.x and 3.21.x branches are ready for cutting patch > releases. > > > On Wed, Dec 6, 2023 at 12:02 PM Claus Ibsen wrote: > >> Hi Gregor >> >> Okay 3.20.x branch is ready for cutting the final release. It will be EOL >> by end of this year. >> I am checking 3.21.x right now. >> >> On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen >> wrote: >> >>> >>> >>> On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski < >>> gre...@list.zurowski.org> wrote: >>> >>>> Hi Claus, >>>> >>>> No worries, I can pick up the 4.3.0 release either this weekend or mid >>>> next week. >>>> >>>> Let's also align on when to start cutting the patch and 3.22 releases. >>>> Can I go ahead and start the final 3.20.9 release immediately, or are >>>> we still waiting on any last patches? >>>> >>>> >>> I am doing some sanity check on 3.20.x right now. I had a power >>> black-out for 1h so I had to do real hard work by showing snow. >>> But power is back, so I will check the 3.20.x and 3.21.x branches and >>> then let you know later so we can start cutting patch releases. >>> And then do 4.3 next week when the elastisearch component is ready. >>> >>> >>> >>>> Thanks, >>>> Gregor >>>> >>>> On Wed, Dec 6, 2023 at 9:57 AM Claus Ibsen >>>> wrote: >>>> > >>>> > Hi Gregor >>>> > >>>> > What does your schedule look like? Would you have best for building >>>> the >>>> > starting on friday, or should we push this out to mid of next week? >>>> > There is a potential new camel-elasticsearch component in the works, >>>> but >>>> > it's not ready yet, but we may get it ready for mid next week. >>>> > However as building and release is a burden on you then we want to >>>> > accommodate what works best for you. >>>> > >>>> > Also it would be good to do final patch releases for 3.20.x as it >>>> goes EOL >>>> > by end of year. >>>> > And also the 3.22.0 release, and maybe a 3.21.x patch release too. >>>> > So there are plenty of old releases as well. >>>> > >>>> > >>>> > >>>> > On Tue, Dec 5, 2023 at 2:42 PM Claus Ibsen >>>> wrote: >>>> > >>>> > > Hi >>>> > > >>>> > > Okay so we have upgraded to Jetty 12, and the core project seems >>>> okay. >>>> > > Federico is checking Camel Spring Boot and reports back when its >>>> okay. >>>> > > >>>> > > There is also the Virtual Threads experiment that Nicolas work on. >>>> > > If merged to main, then this would require for you to build the >>>> release >>>> > > with Java 21. >>>> > > But the generated JARs will work on JDK17 as well. >>>> > > https://github.com/apache/camel/pull/12292 >>>> > > >>>> > > >>>> > > If all goes well we may be ready by friday. We will keep you posted >>>> here. >>>> > > >>>> > > >>>> > > On Sat, Dec 2, 2023 at 7:43 AM Claus Ibsen >>>> wrote: >>>> > > >>>> > >> Hi Gregor >>>> > >> >>>> > >> Thanks. >>>> > >> >>>> > >> Let's see later next week where we are. There is still some work >>>> to do >>>> > >> for the SB 3.2 upgrade. >>>> > >> >>>> > >> >>>> > >> On Wed, Nov 29, 2023 at 9:02 PM Gregor Zurowski < >>>> gre...@list.zurowski.org> >>>> > >> wrote: >>>> > >> >>>> > >>> Any time in December works for me. >>>> > >>> >>>> > >>> >>>> > >>> On Tue, Nov 28, 2023, 3:15 PM Claus Ibsen >>>> wrote: >>>> > >>> >>>> > >>> > Hi >>>> > >>> > >>>> > >>> > It would be good when we have upgraded to Spri
Re: [VOTE] Release Apache Camel 3.20.9 (LTS)
+1 (binding) On Sun, Dec 10, 2023 at 9:16 AM Gregor Zurowski wrote: > Hi Everyone: > > This is a vote to release Apache Camel 3.20.9 (LTS), a final patch > release for the 3.20.x branch with 9 fixes and improvements. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353757=12311211 > > == Apache Camel 3.20.9 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1649/ > > Tarballs: > https://repository.apache.org/content/repositories/orgapachecamel-1649/org/apache/camel/apache-camel/3.20.9/ > > Tag: https://github.com/apache/camel/releases/tag/camel-3.20.9 > > == Apache Camel Spring Boot 3.20.9 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1650/ > > Tag: > https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.20.9 > > == Apache Camel Karaf 3.20.9 == > > Staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1652/ > > Tag: https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.20.9 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.20.9 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.3.0 Release in December
Hi Gregor Okay so both 3.20.x and 3.21.x branches are ready for cutting patch releases. On Wed, Dec 6, 2023 at 12:02 PM Claus Ibsen wrote: > Hi Gregor > > Okay 3.20.x branch is ready for cutting the final release. It will be EOL > by end of this year. > I am checking 3.21.x right now. > > On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen wrote: > >> >> >> On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski >> wrote: >> >>> Hi Claus, >>> >>> No worries, I can pick up the 4.3.0 release either this weekend or mid >>> next week. >>> >>> Let's also align on when to start cutting the patch and 3.22 releases. >>> Can I go ahead and start the final 3.20.9 release immediately, or are >>> we still waiting on any last patches? >>> >>> >> I am doing some sanity check on 3.20.x right now. I had a power black-out >> for 1h so I had to do real hard work by showing snow. >> But power is back, so I will check the 3.20.x and 3.21.x branches and >> then let you know later so we can start cutting patch releases. >> And then do 4.3 next week when the elastisearch component is ready. >> >> >> >>> Thanks, >>> Gregor >>> >>> On Wed, Dec 6, 2023 at 9:57 AM Claus Ibsen >>> wrote: >>> > >>> > Hi Gregor >>> > >>> > What does your schedule look like? Would you have best for building the >>> > starting on friday, or should we push this out to mid of next week? >>> > There is a potential new camel-elasticsearch component in the works, >>> but >>> > it's not ready yet, but we may get it ready for mid next week. >>> > However as building and release is a burden on you then we want to >>> > accommodate what works best for you. >>> > >>> > Also it would be good to do final patch releases for 3.20.x as it goes >>> EOL >>> > by end of year. >>> > And also the 3.22.0 release, and maybe a 3.21.x patch release too. >>> > So there are plenty of old releases as well. >>> > >>> > >>> > >>> > On Tue, Dec 5, 2023 at 2:42 PM Claus Ibsen >>> wrote: >>> > >>> > > Hi >>> > > >>> > > Okay so we have upgraded to Jetty 12, and the core project seems >>> okay. >>> > > Federico is checking Camel Spring Boot and reports back when its >>> okay. >>> > > >>> > > There is also the Virtual Threads experiment that Nicolas work on. >>> > > If merged to main, then this would require for you to build the >>> release >>> > > with Java 21. >>> > > But the generated JARs will work on JDK17 as well. >>> > > https://github.com/apache/camel/pull/12292 >>> > > >>> > > >>> > > If all goes well we may be ready by friday. We will keep you posted >>> here. >>> > > >>> > > >>> > > On Sat, Dec 2, 2023 at 7:43 AM Claus Ibsen >>> wrote: >>> > > >>> > >> Hi Gregor >>> > >> >>> > >> Thanks. >>> > >> >>> > >> Let's see later next week where we are. There is still some work to >>> do >>> > >> for the SB 3.2 upgrade. >>> > >> >>> > >> >>> > >> On Wed, Nov 29, 2023 at 9:02 PM Gregor Zurowski < >>> gre...@list.zurowski.org> >>> > >> wrote: >>> > >> >>> > >>> Any time in December works for me. >>> > >>> >>> > >>> >>> > >>> On Tue, Nov 28, 2023, 3:15 PM Claus Ibsen >>> wrote: >>> > >>> >>> > >>> > Hi >>> > >>> > >>> > >>> > It would be good when we have upgraded to Spring Boot 3.2.0 to >>> do a new >>> > >>> > release in December, so end users can get their hands on latest >>> SB with >>> > >>> > Camel. There is still outstanding work, but I think we would be >>> better >>> > >>> to >>> > >>> > estimate when we are ready next week. Frederico is working on >>> the SB >>> > >>> > upgrade that also requires Jetty upgrades and some other bits. >>> > >>> > >>> > >>> > >>> > >>> > Gregor I wonder what would possibly be the best time for you to >>> cut the >>> > >>> > release? >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > >>> > Claus Ibsen >>> > >>> > - >>> > >>> > @davsclaus >>> > >>> > Camel in Action 2: https://www.manning.com/ibsen2 >>> > >>> > >>> > >>> >>> > >> >>> > >> >>> > >> -- >>> > >> Claus Ibsen >>> > >> - >>> > >> @davsclaus >>> > >> Camel in Action 2: https://www.manning.com/ibsen2 >>> > >> >>> > > >>> > > >>> > > -- >>> > > Claus Ibsen >>> > > - >>> > > @davsclaus >>> > > Camel in Action 2: https://www.manning.com/ibsen2 >>> > > >>> > >>> > >>> > -- >>> > Claus Ibsen >>> > - >>> > @davsclaus >>> > Camel in Action 2: https://www.manning.com/ibsen2 >>> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 4.3.0 Release in December
On Wed, Dec 6, 2023 at 12:30 PM Federico Mariani < federico.mariani.1...@gmail.com> wrote: > Hello, > > I just finished checking tests and examples for camel and > camel-spring-boot, in particular with respect to jetty 12 and spring boot > 3.2 upgrades. > > All the examples can be compiled, tested and run as expected, the only > thing to report is https://issues.apache.org/jira/browse/CAMEL-20195. > Maybe > we should document in the release notes that these components on > camel-spring-boot may be unusable. > > Yes we should add this to the 4.3 upgrade guide. Also you can wonder why does hdfs bring in a http server. > I do not have anything pending regarding jetty 12 or sb 3.2 upgrades, > therefore, camel 4.3 is good to be released from my point of view. > > Regards, > Federico > > Il giorno mer 6 dic 2023 alle ore 12:03 Claus Ibsen > > ha scritto: > > > Hi Gregor > > > > Okay 3.20.x branch is ready for cutting the final release. It will be EOL > > by end of this year. > > I am checking 3.21.x right now. > > > > On Wed, Dec 6, 2023 at 11:48 AM Claus Ibsen > wrote: > > > > > > > > > > > On Wed, Dec 6, 2023 at 10:51 AM Gregor Zurowski < > > gre...@list.zurowski.org> > > > wrote: > > > > > >> Hi Claus, > > >> > > >> No worries, I can pick up the 4.3.0 release either this weekend or mid > > >> next week. > > >> > > >> Let's also align on when to start cutting the patch and 3.22 releases. > > >> Can I go ahead and start the final 3.20.9 release immediately, or are > > >> we still waiting on any last patches? > > >> > > >> > > > I am doing some sanity check on 3.20.x right now. I had a power > black-out > > > for 1h so I had to do real hard work by showing snow. > > > But power is back, so I will check the 3.20.x and 3.21.x branches and > > then > > > let you know later so we can start cutting patch releases. > > > And then do 4.3 next week when the elastisearch component is ready. > > > > > > > > > > > >> Thanks, > > >> Gregor > > >> > > >> On Wed, Dec 6, 2023 at 9:57 AM Claus Ibsen > > wrote: > > >> > > > >> > Hi Gregor > > >> > > > >> > What does your schedule look like? Would you have best for building > > the > > >> > starting on friday, or should we push this out to mid of next week? > > >> > There is a potential new camel-elasticsearch component in the works, > > but > > >> > it's not ready yet, but we may get it ready for mid next week. > > >> > However as building and release is a burden on you then we want to > > >> > accommodate what works best for you. > > >> > > > >> > Also it would be good to do final patch releases for 3.20.x as it > goes > > >> EOL > > >> > by end of year. > > >> > And also the 3.22.0 release, and maybe a 3.21.x patch release too. > > >> > So there are plenty of old releases as well. > > >> > > > >> > > > >> > > > >> > On Tue, Dec 5, 2023 at 2:42 PM Claus Ibsen > > >> wrote: > > >> > > > >> > > Hi > > >> > > > > >> > > Okay so we have upgraded to Jetty 12, and the core project seems > > okay. > > >> > > Federico is checking Camel Spring Boot and reports back when its > > okay. > > >> > > > > >> > > There is also the Virtual Threads experiment that Nicolas work on. > > >> > > If merged to main, then this would require for you to build the > > >> release > > >> > > with Java 21. > > >> > > But the generated JARs will work on JDK17 as well. > > >> > > https://github.com/apache/camel/pull/12292 > > >> > > > > >> > > > > >> > > If all goes well we may be ready by friday. We will keep you > posted > > >> here. > > >> > > > > >> > > > > >> > > On Sat, Dec 2, 2023 at 7:43 AM Claus Ibsen > > > >> wrote: > > >> > > > > >> > >> Hi Gregor > > >> > >> > > >> > >> Thanks. > > >> > >> > > >> > >> Let's see later next week where we are. There is still some work > t
