Re: Why are UnsafeUriCharactersEncoder duplicated?

pendent from > the camel-core. > > > > On Fri, Feb 26, 2016 at 4:09 AM, Tadayoshi Sato > <sato.tadayo...@gmail.com> wrote: > > Hello Camel experts, > > > > I found that there are two UnsafeUriCharactersEncoder classes in the > Camel > >

Why are UnsafeUriCharactersEncoder duplicated?

Hello Camel experts, I found that there are two UnsafeUriCharactersEncoder classes in the Camel codebase, one is in camel-core and another is in camel-catalog, and they are almost identical. Is there any reason these classes need to be duplicated? I like DRY :-) Is it possible to remove the

Re: 3rd party jars not in Maven central, add them to git repository?

Hi Zoran, As Pontus pointed out, for an Apache project 3rd party jars need to be ASL compatible in order to include them into the source repository. To my knowledge, that was the reason why Camel officially doesn't have camel-paypay component: https://issues.apache.org/jira/browse/CAMEL-5093

Re: Time for an overhaul of the patterns symbols?

Hello, Let me offer my thoughts. I think it's a good idea to somehow refresh the EIP icons/diagrams and contribution is always great. However: > the diagrams symbolize the essence of what Camel does. Yes, but it also has a broader context: They actually symbolize the essence of what most of the

Re: Time for an overhaul of the patterns symbols?

Hi Francis, I now fully understand your intention and personally like the idea. (I'm one of the big fans of "flat design" :-) ) As no one else seems to have a strong opinion about it, let me suggest one more idea. As I said EIP diagrams are not proprietary to Camel, I think it's best to provide

camel-itest-karaf is now GREEN

Wow, all camel-itest-karaf tests pass green. Awesome! https://builds.apache.org/blue/organizations/jenkins/Camel.trunk.itest.karaf/activity/ Best regards, Tadayoshi

Re: Build using Maven 3.5.0

Hi, I've started using Maven 3.5.0 recently and so far I haven't found any issues with it on Camel development (I'm using macOS). Once you switch to it you should be amazed that Maven output gets colorful :-) On Sat, Apr 22, 2017 at 5:14 PM, Claus Ibsen wrote: > Hi > > I

Re: Most of camel-itest-osgi removed

ere for > years going untouched and break from time to time. > > We only want a limited few set of tests that does a coarse grained > sanity check of osgi. > > > > > On Thu, Mar 9, 2017 at 1:48 AM, Tadayoshi Sato <sato.tadayo...@gmail.com> > wrote: >> Hi

Most of camel-itest-osgi removed

Hi Camel Devs, I just noticed that most of camel-itest-osgi were removed nearly a year ago. I understand it was due to migration of old itests to the new camel-test-karaf module. But I also suspect that there were indeed some useful itests that had ensured a critical regression wouldn't happen.

Re: Apache Camel 2.19 release blog posts and help spread the word

Hi, I'll write an article summarising the 2.19 features/highlights in Japanese at qiita.com. qiita.com is the hottest knowledge sharing service for techies in Japan. On Wed, Apr 26, 2017 at 4:36 PM, Claus Ibsen wrote: > Hi Jens > > Yes this sounds good. You can post on

Re: Request for Wiki permissions

Thank you, Claus! On Wed, Jun 7, 2017 at 3:27 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi Tada > > I have granted you karma to edit the wikis > > On Wed, Jun 7, 2017 at 2:54 AM, Tadayoshi Sato <sato.tadayo...@gmail.com> > wrote: > > Hello Camel Dev,

Request for Wiki permissions

Hello Camel Dev, I'd like to edit the 2.20.0 release notes so give me permissions for editing the wiki please. https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.20.0+Release My Confluence ID is: tsato Thank you, Tadayoshi

CamelBeanValidatorTest is failing

Looks like CamelBeanValidatorTest in camel-itest-karaf is failing: https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console Tests in error: CamelBeanValidatorTest.test » WrappedTestContainer [test(org.apache.camel.ites... Best regards, Tadayoshi

Re: CamelBeanValidatorTest is failing

t.karaf.CamelBeanValidatorTest > > > > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > &

Re: CamelBeanValidatorTest is failing

://builds.apache.org/job/Camel.trunk.itest.karaf/ so it's hard to detect which one is the culprit. I found this ticket. Was this itest failure the original motivation for the task? https://issues.apache.org/jira/browse/CAMEL-11650 On Thu, Sep 7, 2017 at 10:24 AM, Tadayoshi Sato <sato.tadayo...@gmail.com>

Re: Hosted web site

t` repository and a way to merge from one repository > > to the other (Jenkins job?), but let's make some smaller steps first. > > > > zoran > > > > [1] > https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a99

Hosted web site

Hi all, I've been working on migrating docs, and while there are still a number of pages to be migrated yet it's also becoming in good shape. I think it's good time to host the docs somewhere so that everyone can read and further contribute to the site. I'm aware that recently Francois and Zoran

Re: Create an Apache Camel Twitter Account

So @cameltweet is only for dev, right? +1 for acquiring @ApacheCamel. On Fri, Dec 14, 2018 at 7:24 AM Onder SEZGIN wrote: > +1 > > On Thu, Dec 13, 2018 at 8:26 PM wrote: > > > +1. A twitter account and especially that account name would be nice. > > Am 13. Dez. 2018, 15:49 +0100 schrieb

Re: Camel website

Awesome job, Francois! That's really modern & cool web site! On Tue, Dec 18, 2018 at 9:06 PM Francois Papon wrote: > Cool! > > I will push a PR for the responsive soon. > > Regards, > > François Papon > fpa...@apache.org > > Le 18/12/2018 à 15:51, Zoran Regvart a écrit : > > Thank you

Re: Question about Camel Connector

Could anyone answer this question? I was also surprised to find Camel Connector discontinued in 3.x and would like to get explanation from someone knowledgeable on the topic. I can only find this JIRA other than Claus' commits that deprecated connectors, but the JIRA doesn't refer to any

Re: Quarkus

Hi folks, I like Peter's idea on having a separate repository for camel-quarkus. In addition to his point, I would add that Quarkus is a newly born, cutting edge technology, which itself should evolve fast and likely may not keep how it works now for long as we see in, say, Node.js community.

Re: [VOTE]

Great designs, Jason! I like 1 and 3, with a little more emphasis on 3 :-) Thank you! Tadayoshi On Thu, Apr 25, 2019 at 11:21 AM Nayananga Muhandiram < nayanangamuhandi...@gmail.com> wrote: > +1 for concept three :) > > Thank you, > > *Nayananga Anuradha Muhandiram* > > Batch 11, > Department

Re: [DISCUSS] New Camel website, rump up to go live

The new website looks great. Great job to Zoran and everyone involved in the website renewal! On Fri, Aug 16, 2019 at 2:32 AM Zoran Regvart wrote: > Hi Cameleers, > today I merged the redesign of the front page. I will work on adding a > filter box to the compnents navigation menu

Re: [ANNOUNCEMENT] Brand new Apache Camel website

Congratulations, and well done to all who have been involved in the website renewal!!! On Tue, Aug 20, 2019 at 10:03 PM Zoran Regvart wrote: > Hi Cameleers! > I'm delighted to announce that the new Apache Camel website is live > now. This has been a work that many of you contributed to either >

Where to add Spring Boot integration tests?

Hi folks, I'd like to add an integration test for camel-servlet that can run only on Spring Boot. Initially I thought to add it to tests/camel-itest-spring-boot, but this is rather for systematic compatibility checks for camel components with Spring Boot, not where a real cross-component

Re: Where to add Spring Boot integration tests?

amel-log & camel-rest other than camel-servlet, so it appears that I can put it in camel-servlet-starter. If things grow otherwise and I cannot put it in a single starter project I'll consider other options. Thank you! > > Il giorno gio 12 set 2019 alle ore 12:21 Tadayoshi Sato < >

Re: [HEADSUP] Documentation link checker in the build

yle of cross-referencing? Best regards, Tadayoshi On Wed, Jul 24, 2019 at 11:41 AM Tadayoshi Sato wrote: > Great job Zoran and Nayananga! > > Just to make sure, is now the <> type of cross-referencing > all deprecated and should be rewritten to xref link? Looks like there are >

Re: [HEADSUP] Documentation link checker in the build

Great job Zoran and Nayananga! Just to make sure, is now the <> type of cross-referencing all deprecated and should be rewritten to xref link? Looks like there are still a few leftovers that still use the <> style. Thank you, Tadayoshi On Wed, Jul 24, 2019 at 3:11 AM Zoran Regvart wrote: >

Re: [HEADS UP] - camel3 - camel-http4 renaming to camel-http

+1 Maybe it's also good time to review other components that have similar variants. On Thu, Jul 25, 2019 at 7:09 PM Alex Dettinger wrote: > +1 > > On Thu, Jul 25, 2019 at 12:02 PM Andrea Cosentino > wrote: > > > +1 > > > > Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen < > >

Re: Sending camel-kafka-connector and camel-website github notification mails to camel-commits instead of camel-dev?

> > > > This is an automated message from the Apache Git Service. > > > > To respond to the message, please log on to GitHub and use the > > > > URL above to go to the specific comment. > > > > > > > > For queries about this service, please contact Infrastructure at: > > > > us...@infra.apache.org > > > > > > > > > > > > With regards, > > > > Apache Git Services > > > > > > > > > > > > > -- > Zoran Regvart > -- Tadayoshi Sato

Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released

.apache.org/manual/latest/camel-3-migration-guide.html > [1] http://camel.apache.org/download.html > [2] https://camel.apache.org/blog/release-3-0-0.html > [3] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211 > -- Tadayoshi Sato

Re: Notifications from camel-k & camel-quarkus github repos

orward the github notification to > > commits or notification mailing list instead of flood the dev mailing > > list. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Mon, Oct 7, 2019 at 1:33 PM Tadayoshi Sato > &

Notifications from camel-k & camel-quarkus github repos

Hi folks, I've just realised that this dev mailing list is receiving a huge amount of notifications from camel-k & camel-quarkus github repositories. I am a bit afraid that this overwhelms the actually discussions on camel development here and perhaps is making some who are willing to get

Re: [DISCUSS] - camel-examples git repository

examples as part of their regular build. > > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato

Re: Closing Down on Apache Camel 3.1

t; More camel AWS SDK2 components > > > > > > > > 5) > > > > Camel Main to plugin the new lightweight XML route parser/loader (for > > > > example auto discover on classpath the JAR and use it instead of > JAXB) > > > > > > > > There are other things of course, but these are the bigger high level > > > > things I could remember. > > > > > > > > The usual work with new components, examples, other improvements is > of > > > > course also ongoing. > > > > > > > > Lets see if we can get this done and release Camel 3.1 in February. > > > > > > > > > > > > > > > > > > > > -- > > > > Claus Ibsen > > > > - > > > > http://davsclaus.com @davsclaus > > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > -- Tadayoshi Sato

Re: Merge Commits?

macher > ha > > scritto: > > > >> Hi, > >> > >> recently there were several merge commits (especially for merged pull > >> request). > >> > >> I thought the consensus was to avoid merge commits to keep the git > >> history as clean as possible. > >> > >> Should we keep this policy? > >> > >> What do you think? > >> > >> Cheers, > >> > >> Pascal > >> > >> > >> > > -- Tadayoshi Sato

Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x

JDK etc. > > > > > > > > > -- > > > Claus Ibsen > > > - > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato

Re: [ANNOUNCEMENT] Apache Camel K 1.0.0 released

ho made this release possible. > > > > > > On behalf of the Camel PMC, > > > Nicola Ferraro > > > > > > [1] https://github.com/apache/camel-k/releases/tag/1.0.0 > > > > > -- > -- > Michael Joyner > Solutions Architect > SugarCRM > > mobile: (206)-288-3937 > email: michaelwjoy...@gmail.com > <https://facebook.com/michaelwjoyner>.. > -- Tadayoshi Sato

Re: Are you using binary distribution?

pache/camel-kafka-connector/issues/754__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiVlO1Pqs$ > [3] > https://urldefense.com/v3/__https://www-us.apache.org/dyn/stats/camel.log__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiStt2eyy$ > [4] > https://urldefense.com/v3/__https://www-eu.apache.org/dyn/stats/camel.log__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDicRsFgPE$ > -- > Zoran Regvart > -- Tadayoshi Sato

GitHub API limits hit when building camel-website locally

SON resource " https://api.github.com/repos/apache/camel-k/issues?state=closed=11": Failed to retrieve remote file: Forbidden ... Is there any good way to eschew this issue when developing locally? Thank you, -- Tadayoshi Sato

Re: GitHub API limits hit when building camel-website locally

cached, at least until I ran clean. > So far, I didn't add this information to the documentation about > building the website, so I'll put that on my "to do" list. > > -Karen Lease > > On 17/05/2021 12:11, Tadayoshi Sato wrote: > > Hi folks, > > >

Re: [headsup] Setting GitHub username/token to build the website is required

d#build-the-website-and-antora-theme > -- > Zoran Regvart > -- Tadayoshi Sato

Re: Camel code generator for the Camel web site

Hello Camel Developers, > > > > > > > > > > > > I would like to propose to add a code generator to the Camel web > > site > > > > > > to simplify (archetypes, versions, components, etc) the project > > > > creation > > > > > > process for developers. > > > > > > > > > > > > I have developed a prototype https://kameleon.dev > > > > > > It could be used as a starting point. > > > > > > > > > > > > Thank you and have a nice day > > > > > > Marat Gubaidullin > > > > > > > > > > > > > > > > > > > > -- > > > > > Zoran Regvart > > > > > > > > > > > > > > > > -- > > > > Zoran Regvart > > > > > > > > > > > > > -- > > > Otavio R. Piske > > > http://orpiske.net > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel-kafka-connector 0.9.0

release (provide specific comments) > > The vote is open for at least 48 hours. > > Thanks, > Andrea. > -- Tadayoshi Sato

Re: Camel 3 - More middle folders in components

gt; > - debezium > > - microprofile (all microprpofile modules) > > - spring (all spring modules) > > - test (unit test and testcontainers) > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > -- Tadayoshi Sato

Re: [HEADS UP] - Optional property placeholders in Camel 3.9

it clashes with this. > > But we could make "optional" a reserved word and do special handling > > for this. > > > > The only concern about using ? is that an endpoint uri already have ? > > for query parameters. And if using more ? would be confusing? > > > > > from("jms:cheese?concurrentConsumers={{?speedUp}}={{someName}}") > > > > Any thoughts? > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Zoran Regvart > -- Tadayoshi Sato

Re: [HEADS UP] - Optional property placeholders in Camel 3.9

he ? mark was choose to keep it short. But we are >> > open for feedback. >> > Another alternative was to prefix with optional: >> > >> > {{optional:speedUp}} >> > >> > However the properties component in Camel then assume the key is named >> > optional, and the default value is speedUp. So it clashes with this. >> > But we could make "optional" a reserved word and do special handling >> > for this. >> > >> > The only concern about using ? is that an endpoint uri already have ? >> > for query parameters. And if using more ? would be confusing? >> > >> > >> from("jms:cheese?concurrentConsumers={{?speedUp}}={{someName}}") >> > >> > Any thoughts? >> > >> > >> > -- >> > Claus Ibsen >> > - >> > http://davsclaus.com @davsclaus >> > Camel in Action 2: https://www.manning.com/ibsen2 >> >> >> >> -- >> Zoran Regvart >> > > > -- > Tadayoshi Sato > -- Tadayoshi Sato

Re: [discuss] find a better name for KameletBinding

re appropriate and to > reduce > > > confusion, we should try to find a better name. > > > > > > On top of my mind, I'd see the following names as a possible > replacement: > > > - Binding so leave Kamelet out of the game as Kamelets are one of the > > > option but not the exclusive on > > > - Connector as in essence, a KameletBinding describe how to connect A > to B > > > > > > Any opinion ? > > > > > > --- > > > Luca Burgazzoli > > > > > > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato

Re: [Website] Better error checking

826] WARN (asciidoctor): skipping reference to missing > attribute: lookahead > > file: docs/modules/ROOT/pages/kamelets/kamelets-dev.adoc > > source: https://github.com/apache/camel-k.git (refname: > release-1.4.x, start path: docs) > > [22:45:49.828] WARN (asciidoctor): skipping reference to missing > attribute: period > > file: docs/modules/ROOT/pages/kamelets/kamelets-dev.adoc > > source: https://github.com/apache/camel-k.git (refname: > release-1.4.x, start path: docs) > > [22:45:54.820] WARN (asciidoctor): skipping reference to missing > attribute: body > > file: docs/modules/ROOT/pages/reference/extensions/core.adoc > > source: https://github.com/apache/camel-quarkus.git (refname: main, > start path: docs) > > [22:45:59.069] WARN (asciidoctor): skipping reference to missing > attribute: body > > file: docs/modules/ROOT/pages/reference/extensions/core.adoc > > source: https://github.com/apache/camel-quarkus.git (refname: > release/2.0.0, start path: docs) > > > > > > Currently this sort of warning is output to the console but cannot be > used to fail the build. > > > > David Jencks > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato

Re: Dropping Java 8

s are starting to drop JDK 8 in favor > > of > > > JDK 11 (last one I've found is Optaplanner). > > > > > > I think we need to define a release where we totally drop Java 8 > Support > > > and start to build and release with Java 11 only. > > > > > > What are your thoughts? > > > > > > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.6.1 and related libraries

ssible to install all staging artifacts with a single command: > > > > kamel install --operator-image camelk/camel-k:1.6.1 > --maven-repository > > > > > https://repository.apache.org/content/repositories/orgapachecamel-1369 > > > > --olm=false > > > > > > > > Please test this release candidate and cast your vote. > > > > > > > > [ ] +1 Release the binary as Apache Camel K 1.6.1 and > > > > Apache Camel K Runtime 1.9.1 > > > > [ ] -1 Veto the release (provide specific comments) > > > > > > > > The vote is open for at least 72 hours. > > > > > > > > Here's my +1. > > > > > > > > Thanks, > > > > Nicola Ferraro > > > > > > > > > > -- > > Otavio R. Piske > > http://orpiske.net > > > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.8.0 and related libraries

pache Camel K 1.8.0, Apache Camel K Runtime > 1.11.0 and Apache Camel Kamelets 0.7.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: GitHub discussions for Apache Camel project

/help, and another space where we can have roadmap and > design/tech discussions etc. > > For big organisational decisions and whatnot, > then we should still use the DEV mailing list. > > Any thoughts? > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.9.0 and related libraries

https://repository.apache.org/content/repositories/orgapachecamel-1427 > > --olm=false > > > > Please test this release candidate and cast your vote. > > > > [ ] +1 Release the binary as Apache Camel K 1.9.0, Apache Camel K Runtime > > 1.13.0 and Apache Camel Kamelets 0.8.0 > > [ ] -1 Veto the release (provide specific comments) > > > > The vote is open for at least 72 hours. > > > > Here's my +1. > > > > Thanks, > > Andrea Cosentino > > > -- Tadayoshi Sato

Re: Camel K 1.9.0 Release

I just found one bug in Camel K CLI: https://github.com/apache/camel-k/issues/3203 It doesn't look cool and IMO is better to be fixed before 1.9.0. On Thu, Apr 14, 2022 at 12:37 PM Tadayoshi Sato wrote: > +1 > > Thanks Andrea! > > On Wed, Apr 13, 2022 at 6:23 PM Andrea Cos

Re: Camel K 1.9.0 Release

and start the vote. > > Any thoughts? > > Thanks. > -- Tadayoshi Sato

Re: Camel K 1.9.0 Release

FYI: https://github.com/apache/camel-k/pull/3204 On Thu, Apr 14, 2022 at 3:20 PM Tadayoshi Sato wrote: > I just found one bug in Camel K CLI: > https://github.com/apache/camel-k/issues/3203 > > It doesn't look cool and IMO is better to be fixed before 1.9.0. > > On Thu, Apr 14

Re: [VOTE] Release Apache Camel Kamelets 0.9.2

l-kamelets 0.9.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 48 hours. > > NOTE: The vote for 48 hours is because there are no breaking changes but > the release is not really urgent. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: Extend LTS concept to Camel K

[1] seems to have a LTS > > too, but there is no camel-k-runtime LTS. > > In this case the LTS concept would be extended to camel-k-runtime and > > sync the Camel K LTS with the camel quarkus/camel LTS releases ? > > > > 1. https://camel.apache.org/camel-quarkus/next/index.html > > > > -- > > Claudio Miranda > > > > clau...@claudius.com.br > > http://www.claudius.com.br > > > -- Tadayoshi Sato

Re: Extend LTS concept to Camel K

bility. > > Please, share your feedback. > > Regards, > Pasquale. > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.10.0 and related libraries

binary as Apache Camel K 1.10.0, Apache Camel K Runtime > 1.14.0 and Apache Camel Kamelets 0.9.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.11.0 and related libraries

binary as Apache Camel K 1.11.0, Apache Camel K Runtime > 1.16.0 and Apache Camel Kamelets 0.10.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel 3.20.0 (LTS)

el-karaf-3.20.0 > > Please test this release candidate and cast your vote: > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > Karaf 3.20.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Thanks, > Gregor > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel 3.20.0 (LTS)

gt; > > https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.20.0 > > > > > > Please test this release candidate and cast your vote: > > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel > > > Karaf 3.20.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 > > > -- Tadayoshi Sato

Re: [HEADS UP] Camel-Kamelets moving to 3.20.0 version

no > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel Kamelets 3.20.0

ote. > > [ ] +1 Release camel-kamelets 3.20.0 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: Evolution of Kamelets

> > > lot > > > > of stuff to improve. > > > > > > > > In my opinion we should work on multiple sides: > > > > - make it possible to load different kamelet catalogs (complex cases, > > > > custom kamelets, etc.) > > > > - improve the default Kamelets catalog > > > > - Focus on the camel-jbang experience > > > > - Maybe try to think about a Kamelets Marketplace or catalog > > marketplace > > > > > > > > My proposal is also to note in terms of documentation that kamelets > are > > > not > > > > only tied to Camel K, but some fundamental building block in the > Camel > > > > experience. > > > > > > > > I think we should create some epic around this and try to follow this > > > path. > > > > > > > > Any feedback, comments and thoughts are welcome. Please let me know > > what > > > > you think. > > > > > > > > Cheers, > > > > Andrea > > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > Otavio R. Piske > http://orpiske.net > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel Kamelets 0.9.3

; [ ] +1 Release camel-kamelets 0.9.3 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato

Re: [VOTE] Release Apache Camel K 1.10.3 and Camel K Runtime 1.15.2

es/orgapachecamel-1495 > --olm=false > > Please test this release candidate and cast your vote. > > [ ] +1 Release the binary as Apache Camel K 1.10.3 and > Apache Camel K Runtime > 1.15.2 > [ ] -1 Veto the release (provide specific comments) > > The vote is open for at least 72 hours. > > Here's my +1. > > Thanks, > Andrea Cosentino > -- Tadayoshi Sato