Re: [VOTE] Release Apache Camel Kamelets 4.0.0-RC1
+1 (binding) Thanks Andrea Zineb Bendhiba > Le 5 juil. 2023 à 12:24, Andrea Cosentino a écrit : > > Hello all, > > This is a vote for releasing camel-kamelets 4.0.0-RC1 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1589 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.0-RC1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino
Re: [VOTE] Release Apache Camel Kamelets 4.0.0-RC1
+1 (binding) Thanks! On Wed, Jul 5, 2023 at 12:24 PM Andrea Cosentino wrote: > Hello all, > > This is a vote for releasing camel-kamelets 4.0.0-RC1 > > Kamelets release files: > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1 > Kamelets staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1589 > Kamelets Tag: > https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1 > > Please cast your vote. > > [ ] +1 Release camel-kamelets 4.0.0-RC1 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino >
[VOTE] Release Apache Camel Kamelets 4.0.0-RC1
Hello all, This is a vote for releasing camel-kamelets 4.0.0-RC1 Kamelets release files: https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1 Kamelets staging repository: https://repository.apache.org/content/repositories/orgapachecamel-1589 Kamelets Tag: https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1 Please cast your vote. [ ] +1 Release camel-kamelets 4.0.0-RC1 [ ] -1 Veto the release (provide specific comments) The vote is open for at least 72 hours. Here's my +1. Thanks, Andrea Cosentino
Re: [VOTE] Release Camel K Runtime 2.16.0
On Wed, Jul 5, 2023 at 10:20 AM Claus Ibsen wrote: > Hi > > What is the reason for the bump of the version (besides aligning to a > Quarkus version)? > Is this intended for Camel K 1.x or whats the need for this release? Hi Claus, this version will be required by Camel K version 2 only. As I mentioned earlier, we've worked to decouple the release process, as Camel K will be able to run any Camel K runtime > 1.15.0 starting from version 2. The idea is that this runtime version will be the default one we'll use for incoming Camel K version 2 release, so, in order to use a final runtime release, we need this release process to start before. Once the vote passes and the release is confirmed we'll be able to start the release process for Camel K 2.0. Any future Camel K runtime (ie, version 3, once Camel Quarkus is available) should be able to be run by Camel K 2 without the need to release the operator (it should be forward compatible). The trick will be to use `-t camel.runtime-version=3.0.0` and the operator will build a dynamic catalog which will take care of all building aspects. For this reason, in the future I'll expect that we will release the Camel K Runtime always independently from the Camel K Operator project. We have also started some discussion to understand if/how to include it in Camel Quarkus directly, but, for the time being, we'll proceed with a separate release, right after Camel Quarkus is released. Hope it clarifies. Cheers, Pasquale. > > On Tue, Jul 4, 2023 at 10:45 AM Pasquale Congiusti < > pasquale.congiu...@gmail.com> wrote: > > > Hello, > > > > This is a vote to release Camel K Runtime 2.16.0. This release mostly > > contains the runtime artifacts required for Camel K version 2 to be > > released independently. As the Camel K Runtime depends mostly on Camel > > Quarkus, we've aligned the version to the same used in Camel Quarkus. > From > > now on we expect to release Camel K Runtime beside Camel Quarkus and have > > an available runtime for Camel K as soon as the runtime is released. > > > > Camel K Runtime source files: > > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/2.16.0/ > > > > Camel K Runtime staging repository: > > https://repository.apache.org/content/repositories/orgapachecamel-1587 > > > > Camel K Runtime Tag: > > > > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-2.16.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 (2.16.0): > > > > kamel install --maven-repository= > > https://repository.apache.org/content/repositories/orgapachecamel-1587 > > --olm=false > > ... > > > > kamel run Test.java -t camel.runtime-version=2.16.0 > > > > > > Please test this release candidate and cast your vote. > > > > [ ] +1 Release Apache Camel K Runtime 2.16.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 > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [VOTE] Release Camel K Runtime 2.16.0
Hi What is the reason for the bump of the version (besides aligning to a Quarkus version)? Is this intended for Camel K 1.x or whats the need for this release? On Tue, Jul 4, 2023 at 10:45 AM Pasquale Congiusti < pasquale.congiu...@gmail.com> wrote: > Hello, > > This is a vote to release Camel K Runtime 2.16.0. This release mostly > contains the runtime artifacts required for Camel K version 2 to be > released independently. As the Camel K Runtime depends mostly on Camel > Quarkus, we've aligned the version to the same used in Camel Quarkus. From > now on we expect to release Camel K Runtime beside Camel Quarkus and have > an available runtime for Camel K as soon as the runtime is released. > > Camel K Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/2.16.0/ > > Camel K Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1587 > > Camel K Runtime Tag: > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-2.16.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 (2.16.0): > > kamel install --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1587 > --olm=false > ... > > kamel run Test.java -t camel.runtime-version=2.16.0 > > > Please test this release candidate and cast your vote. > > [ ] +1 Release Apache Camel K Runtime 2.16.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 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [VOTE] Release Camel K Runtime 2.16.0
+1 (non-binding) Thanks! Gaëlle Le mar. 4 juil. 2023 à 10:45, Pasquale Congiusti < pasquale.congiu...@gmail.com> a écrit : > Hello, > > This is a vote to release Camel K Runtime 2.16.0. This release mostly > contains the runtime artifacts required for Camel K version 2 to be > released independently. As the Camel K Runtime depends mostly on Camel > Quarkus, we've aligned the version to the same used in Camel Quarkus. From > now on we expect to release Camel K Runtime beside Camel Quarkus and have > an available runtime for Camel K as soon as the runtime is released. > > Camel K Runtime source files: > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/2.16.0/ > > Camel K Runtime staging repository: > https://repository.apache.org/content/repositories/orgapachecamel-1587 > > Camel K Runtime Tag: > > https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-2.16.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 (2.16.0): > > kamel install --maven-repository= > https://repository.apache.org/content/repositories/orgapachecamel-1587 > --olm=false > ... > > kamel run Test.java -t camel.runtime-version=2.16.0 > > > Please test this release candidate and cast your vote. > > [ ] +1 Release Apache Camel K Runtime 2.16.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 >
Re: Jetty HttpServletResponse sendRedirect
Hi You can try with setting a Camel header with the Exchange.HTTP_STATUS_CODE to the 3xx value for redirect, and another header with the location (using the standard name for that). And then an empty body. On Tue, Jun 27, 2023 at 3:44 PM Fyodor Kravchenko wrote: > Hello, > > one of my producers runs a custom script that is allowed to get access > to the HttpServletRequest and to invoke sendRedirect method on it. It > used to work on Camel 2 but with Camel 3.20.4 Jetty tells this: > > 16:19:38.178 [qtp987805552-43] ERROR > o.a.camel.component.jetty.CamelContinuationServlet - Error processing > request > org.eclipse.jetty.io.EofException: Closed > at > org.eclipse.jetty.server.HttpOutput.checkWritable(HttpOutput.java:771) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:795) > at org.apache.camel.util.IOHelper.copy(IOHelper.java:206) > at org.apache.camel.util.IOHelper.copy(IOHelper.java:161) > at > > org.apache.camel.http.common.DefaultHttpBinding.copyStream(DefaultHttpBinding.java:500) > at > > org.apache.camel.http.common.DefaultHttpBinding.doWriteDirectResponse(DefaultHttpBinding.java:566) > at > > org.apache.camel.http.common.DefaultHttpBinding.doWriteResponse(DefaultHttpBinding.java:439) > at > > org.apache.camel.http.common.DefaultHttpBinding.writeResponse(DefaultHttpBinding.java:362) > > A quick look at the DefaultHttpBinding.writeResponse shows it doesn't > check for HttpServletRequest.isCommitted(), only for the body to be blanc. > > Is there any solution to allow users to send redirects in their scripts > in the processors? Couldn't find a dedicated Camel HttpMessage method > for that. > > --fedd > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
