[Camel 4.4.1] Issue with REST clientRequestValidation and fix proposal

Hello, For one of our projects, we offer a set of REST/JSON APIs using Camel and wanted to activate the clientRequestValidation feature on those endpoints for Camel to reject invalid requests. But we encountered some limitations due to the way RestBindingAdvice handles the Accept header when the

Re: Proposal for improving the way we collaborate on code improvements

Hi, On Mon, Jul 24, 2023 at 9:47 AM Claus Ibsen wrote: > Hi > > Ad 1) > For basic stuff like a polish or update in a readme / doc file then direct > push can be okay. > > However the GA action has improved a lot in recent time, so the time it > takes for it to complete and the feedback it gives

Re: Proposal for improving the way we collaborate on code improvements

Hi Andrea, Thanks! After we get a consensus, I'll make sure we document that on the contributor guidelines, so we have something to refer to and everyone knows the expectations. Kind regards On Wed, Jul 19, 2023 at 10:47 AM Andrea Cosentino wrote: > Hello Otavio, > > I'm answering inline. > >

Re: Proposal for improving the way we collaborate on code improvements

Hi Ad 1) For basic stuff like a polish or update in a readme / doc file then direct push can be okay. However the GA action has improved a lot in recent time, so the time it takes for it to complete and the feedback it gives now is more trustworthy. Ad 2) Yes this is good practice to squash -

Re: Proposal for improving the way we collaborate on code improvements

Hi, +1 with this proposal, thx Otavio Regards, Nicolas From: Otavio Rodolfo Piske Sent: Wednesday, July 19, 2023 10:38 To: dev Subject: Proposal for improving the way we collaborate on code improvements Hi folks, I am writing this proposed changes based

Re: Proposal for improving the way we collaborate on code improvements

Hello Otavio, I'm answering inline. Il giorno mer 19 lug 2023 alle ore 10:38 Otavio Rodolfo Piske < angusyo...@gmail.com> ha scritto: > Hi folks, > > I am writing this proposed changes based on the feedback received on the > previous email where I shared some thoughts/concerns about improving

Proposal for improving the way we collaborate on code improvements

Hi folks, I am writing this proposed changes based on the feedback received on the previous email where I shared some thoughts/concerns about improving our contribution practices (see the email entitled "Some thoughts on bisecting Camel and our git commit practices" for details). This is mostly

Re: proposal: merge camel-k-runtime into camel-quarkus

On Sat, Nov 19, 2022 at 7:55 AM Otavio Rodolfo Piske wrote: > > Although I do have some concerns of > appropriateness of some code that now lies in Camel K runtime, I think it's > a matter of adjusting them to be more generic or moving them up or down to > Camel Core or Camel K as needed. Sure,

Re: proposal: merge camel-k-runtime into camel-quarkus

Hi Claudio, I think the approach is fine. I also agree the change to Camel Quarkus can make things easier for Camel K. Although I do have some concerns of appropriateness of some code that now lies in Camel K runtime, I think it's a matter of adjusting them to be more generic or moving them up or

Re: proposal: merge camel-k-runtime into camel-quarkus

Hi +1 Yes this would be really good. On Thu, Nov 17, 2022 at 3:17 PM Claudio Miranda wrote: > Hi, camel-k-runtime project was created to have several camel > components (and the related quarkus extensions) suitable for Camel K, > however all camel components are already into camel, and only

proposal: merge camel-k-runtime into camel-quarkus

Hi, camel-k-runtime project was created to have several camel components (and the related quarkus extensions) suitable for Camel K, however all camel components are already into camel, and only the quarkus extensions are in camel-k-runtime. Today we have to manage camel-k-runtime releases and

Re: [PROPOSAL] Refactoring and new maintenance of camel-karaf

Hey JB- These sound really good! Especially whiteboard support and simplified deployment of dependencies. Thanks! Matt Pavlovich > On May 2, 2022, at 8:07 AM, Jean-Baptiste Onofré wrote: > > Hi guys, > > I worked on several changes on camel-karaf that I would like to > propose as PR asap: >

Re: [PROPOSAL] Refactoring and new maintenance of camel-karaf

Hi Claus, I agree, it sounds good to me. Let me move forward on the PRs, and we will merge timing wise ;) Thanks, Regards JB On Sun, May 8, 2022 at 10:40 AM Claus Ibsen wrote: > > Hi JB > > We are closing in towards the next LTS release of Apache Camel that > will be 3.18.0 to be released in

Re: [PROPOSAL] Refactoring and new maintenance of camel-karaf

Hi JB We are closing in towards the next LTS release of Apache Camel that will be 3.18.0 to be released in July 2022. Next week we finish up the bits to be ready for doing the 3.17.0 release. In light of this then I suggest that your work is targeted after the 3.18 LTS release, which gives you

Re: [PROPOSAL] Refactoring and new maintenance of camel-karaf

Hi guys, As I didn't receive any objections about this one, I will move forward and open the PRs. Regards JB On Mon, May 2, 2022 at 3:07 PM Jean-Baptiste Onofré wrote: > > Hi guys, > > I worked on several changes on camel-karaf that I would like to > propose as PR asap: > > Short term (now): >

[PROPOSAL] Refactoring and new maintenance of camel-karaf

Hi guys, I worked on several changes on camel-karaf that I would like to propose as PR asap: Short term (now): 1. Remove platform module to directly use features module I've removed the platform maven module, and moved camel-karaf features directly in a new features module (as we do directly in

Re: [PROPOSAL] Remove activemq-camel component

The report would be helpful then. On Sat, Jan 15, 2022 at 1:13 AM Jean-Baptiste Onofre wrote: > OK thanks. > > Actually, I know cherry-pick -x / cherry-pick -e pretty well ;) > > I’m using it for a while when back porting from main to activemq-5.xx.x > branches (and in bunch of others Apache

Re: [PROPOSAL] Remove activemq-camel component

OK thanks. Actually, I know cherry-pick -x / cherry-pick -e pretty well ;) I’m using it for a while when back porting from main to activemq-5.xx.x branches (and in bunch of others Apache projects) ;) Regards JB > Le 15 janv. 2022 à 06:51, Clebert Suconic a écrit > : > > I’m talking more

Re: [PROPOSAL] Remove activemq-camel component

I’m talking more about a general point orthogonal to this discussion. When you back port commits. If you used git cherry pick -x I have a report to help track commits between branches. On Fri, Jan 14, 2022 at 11:50 PM JB Onofré wrote: > Hi Clebert > > We know but these point here was more

Re: [PROPOSAL] Remove activemq-camel component

Hi Clebert We know but these point here was more a discussion to the community if it makes sense to remove the component in 5.16.x. And actually it’s something we discussed in the original PR (I forgot): we agreed to remove on for coming 5.17.x releases. Regards JB > Le 14 janv. 2022 à

Re: [PROPOSAL] Remove activemq-camel component

you guys should use cherry-pick -x between main and 5.16.x then you could use this type of reporting I'm generating for between main and 2.19.x on activemq artemis. it's fairly helpful I think. easier to manage what's missing between the branches... let me know if you need some help using

Re: [PROPOSAL] Remove activemq-camel component

Ok I remember the discussion now. Let’s keep it in 5.16.x and focus on 5.17.0 where it’s already removed. Sorry about the noise ;) Regards JB > Le 12 janv. 2022 à 16:06, Jean-Baptiste Onofre a écrit : > > Yes, I know: my point is also to remove from activemq-5.16.x > > If no objection, I

Re: [PROPOSAL] Remove activemq-camel component

Yes, I know: my point is also to remove from activemq-5.16.x If no objection, I will remove it from there. Thanks, Regards JB > Le 12 janv. 2022 à 16:03, Matt Pavlovich a écrit : > > Hey JB- > > I already removed it from 5.17.0 (main) > > -Matt > >> On Jan 12, 2022, at 4:16 AM,

Re: [PROPOSAL] Remove activemq-camel component

Hey JB- I already removed it from 5.17.0 (main) -Matt > On Jan 12, 2022, at 4:16 AM, Jean-Baptiste Onofré wrote: > > Hi all, > > ActiveMQ provides activemq-camel component. > > This component is "old" (using Camel 2.25.x) and has been replaced by > camel-activemq and/or camel-jms. > > I

[PROPOSAL] Remove activemq-camel component

Hi all, ActiveMQ provides activemq-camel component. This component is "old" (using Camel 2.25.x) and has been replaced by camel-activemq and/or camel-jms. I propose to remove ActiveMQ Camel from the ActiveMQ code. Thoughts ? Regards JB

Re: [PROPOSAL] Remove activemq-camel from Apache ActiveMQ

activemq-camel component from Apache ActiveMQ. >>> >>> Since Camel 3.x, Camel provides camel-activemq component (with the >>> corresponding Apache Karaf feature), and also, >>> camel-jms/camel-amqp/camel-mqtt work fine with ActiveMQ. >>> So, I think that activemq-camel component is not useless, and it’s still >>> using camel 2.x. >>> >>> My proposal is to remove activemq-camel and cleanup the headers in >>> activemq-osgi. >>> >>> Thoughts ? >>> >>> Regards >>> JB >> >

Re: [PROPOSAL] Remove activemq-camel from Apache ActiveMQ

rom Apache ActiveMQ. >> >> Since Camel 3.x, Camel provides camel-activemq component (with the >> corresponding Apache Karaf feature), and also, >> camel-jms/camel-amqp/camel-mqtt work fine with ActiveMQ. >> So, I think that activemq-camel component is not u

Re: [PROPOSAL] Remove activemq-camel from Apache ActiveMQ

el 3.x, Camel provides camel-activemq component (with the >> corresponding Apache Karaf feature), and also, >> camel-jms/camel-amqp/camel-mqtt work fine with ActiveMQ. >> So, I think that activemq-camel component is not useless, and it’s still >> using camel 2.x. >> >> My proposal is to remove activemq-camel and cleanup the headers in >> activemq-osgi. >> >> Thoughts ? >> >> Regards >> JB >

Re: [PROPOSAL] Remove activemq-camel from Apache ActiveMQ

ponent from Apache ActiveMQ. > > Since Camel 3.x, Camel provides camel-activemq component (with the > corresponding Apache Karaf feature), and also, > camel-jms/camel-amqp/camel-mqtt work fine with ActiveMQ. > So, I think that activemq-camel component is not useless, and it’s still &g

[PROPOSAL] Remove activemq-camel from Apache ActiveMQ

work fine with ActiveMQ. So, I think that activemq-camel component is not useless, and it’s still using camel 2.x. My proposal is to remove activemq-camel and cleanup the headers in activemq-osgi. Thoughts ? Regards JB

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Hi Gavin, no issues with this for Camel, thank you :) zoran On Sat, Oct 17, 2020 at 12:35 PM Gavin McDonald wrote: > > Hi All, > > So I'm working through this today. I tested on the ci-infra instance and it > seems to the tool locations > checkboxes just disappear after the renaming. But they

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Hi All, Ok, I'm done for now, please test everyone. On Sat, Oct 17, 2020 at 12:34 PM Gavin McDonald wrote: > Hi All, > > So I'm working through this today. I tested on the ci-infra instance and > it seems to the tool locations > checkboxes just disappear after the renaming. But they are

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Hi All, So I'm working through this today. I tested on the ci-infra instance and it seems to the tool locations checkboxes just disappear after the renaming. But they are still in the on disk configuration, causing not found errors. So I will have to do a find/replace on those items as well.

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Sorry, still on, I'll get it done today. On Tue, Oct 13, 2020 at 8:46 AM Zoran Regvart wrote: > Hi Gavin, > from what I can see this hasn't happened yet. I'm guessing the plan is > still on, but postponed? > > zoran > > On Sun, Oct 11, 2020 at 2:03 PM Gavin McDonald > wrote: > > > > As there

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Hi Gavin, from what I can see this hasn't happened yet. I'm guessing the plan is still on, but postponed? zoran On Sun, Oct 11, 2020 at 2:03 PM Gavin McDonald wrote: > > As there have been no objections, I will be making this change tomorrow > afternoon UTC at around 5PM > > > > On Thu, Sep 24,

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

eed to update our build configuration. For example here[1] >>> >>> zoran >>> [1] >>> https://github.com/apache/camel/blob/62739be4b1cd63dd4504e88e95868f952cab41ca/Jenkinsfile#L21 >>> >>> ------ Forwarded message - >>> From: Gavin

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

t;> -- Forwarded message - >> From: Gavin McDonald >> Date: Wed, Sep 23, 2020 at 7:51 PM >> Subject: [PROPOSAL] - Change the Descriptions to installed packages on >> Jenkins >> To: builds >> >> >> Hi All, >> >> This is i

Re: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

b.com/apache/camel/blob/62739be4b1cd63dd4504e88e95868f952cab41ca/Jenkinsfile#L21 > > -- Forwarded message - > From: Gavin McDonald > Date: Wed, Sep 23, 2020 at 7:51 PM > Subject: [PROPOSAL] - Change the Descriptions to installed packages on > Jenkins > To: builds

Fwd: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins

Date: Wed, Sep 23, 2020 at 7:51 PM Subject: [PROPOSAL] - Change the Descriptions to installed packages on Jenkins To: builds Hi All, This is in response to https://issues.apache.org/jira/browse/INFRA-20858 but has also been mentioned previously over the years. This proposal is in relation

Re: [HEADS UP/PROPOSAL] "New" Camel Karaf for 3.5.0

Hi JB, I think it make a lot of senses, especially to help users to build a custom Karaf/Camel distribution! regards, François fpa...@apache.org Le 22/06/2020 à 19:09, Jean-Baptiste Onofre a écrit : > Hi guys, > > Now that Camel Karaf is on its own repository, I started major >

Re: [HEADS UP/PROPOSAL] "New" Camel Karaf for 3.5.0

Hi Guillaume, Thanks for your feedback, see my comments inline: > Le 23 juin 2020 à 02:51, Guillaume Nodet a écrit : > > Le lun. 22 juin 2020 à 19:09, Jean-Baptiste Onofre > a > écrit : > >> Hi guys, >> >> Now that Camel Karaf is on its own repository, I started

Re: [HEADS UP/PROPOSAL] "New" Camel Karaf for 3.5.0

Le lun. 22 juin 2020 à 19:09, Jean-Baptiste Onofre a écrit : > Hi guys, > > Now that Camel Karaf is on its own repository, I started major > refactoring/improvement coming for 3.5.0 (as 3.4.0 is LTS): > > 1. Cleanup > I did a complete module structure cleanup (no platform anymore, core > module

[HEADS UP/PROPOSAL] "New" Camel Karaf for 3.5.0

Hi guys, Now that Camel Karaf is on its own repository, I started major refactoring/improvement coming for 3.5.0 (as 3.4.0 is LTS): 1. Cleanup I did a complete module structure cleanup (no platform anymore, core module directly at root folder) and feature. 2. Remove osgi-activator component

Re: GSoC 2020: Congratulations, your proposal with The Apache Software Foundation has been accepted!

Hi Juan, sounds good. Glad to have you contributing :) zoran On Tue, May 5, 2020 at 5:46 AM Juan Segarra wrote: > > Hi folks. > > I received the acceptance e-mail for my GSoC proposal. Thanks your for your > confidence in my project, support and feedback. > > I was checking

Fwd: GSoC 2020: Congratulations, your proposal with The Apache Software Foundation has been accepted!

Hi folks. I received the acceptance e-mail for my GSoC proposal. Thanks your for your confidence in my project, support and feedback. I was checking out the camel-oaipmh[1] repository and I realized that Carlos nicely has already changed the project to the Apache License. So, I think I could

Re: [GSoC 2020] Apache Camel - OAI-PMH Proposal draft

Hi Thanks for your all comments on my proposal, they really helped me to polish it. I have sent the final document to GSoC, however, if you have more ideas or suggestions I can update my proposal until the day 31. Thanks for your time. Best regards, Juan El mié., 18 mar. 2020 a las 2:28

Re: [GSoC 2020] Apache Camel - OAI-PMH Proposal draft

Looks good, thanks for posting the proposal. -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, March 18, 2020, 01:07:42 AM GMT+1, Juan

[GSoC 2020] Apache Camel - OAI-PMH Proposal draft

Hi all. Firstly, I really hope that all of you and your loved ones are fine and this awful pandemic situation ends soon. Secondly, I have created an google docs document with my proposal for an OAI-PMH component for Apache Camel considering all the thing that we discussed in the mailing list [1

Re: GSoC project proposal

Hi Kirill, your proposal looks good, make sure that you do submit it at the GSoC. To get started and to better acquaint ourselves, we encourage (small) contributions to Camel, but it's not a strict requirement. We have some easy and help wanted tasks linked from the contributing page here: https

Re: GSoC project proposal

The proposal must be submitted on the gsoc site by the student. We don't expect more from a student, in my opinion the proposal is already complete. Il giorno mer 4 mar 2020 alle ore 12:16 Kirill Yankov < myworkpost...@gmail.com> ha scritto: > Dear mentors, > > Can you ple

Re: GSoC project proposal

Dear mentors, Can you please give e some guidelines: - After I’ve made a proposal who should finally confirm it? (link to the proposal: https://github.com/manonthegithub/GSoC-2020/blob/master/camel/Proposal.md) - Do you expect something else from a student to be successfully accepted? Thank

Re: GSoC project proposal

reate also some > spring-boot-starter for them here[1] > > Looks good to me globally > > [1] https://github.com/apache/camel-spring-boot > > Il giorno lun 2 mar 2020 alle ore 14:24 Kirill Yankov < > myworkpost...@gmail.com> ha scritto: > >> Hey everyone! >

Re: GSoC project proposal

Kirill Yankov < myworkpost...@gmail.com> ha scritto: > Hey everyone! > > I have made a first version of my proposal for GSoC project with Camel. > Please take a look and give your comments. > https://github.com/manonthegithub/GSoC-2020/blob/master/camel/Proposal.md

GSoC project proposal

Hey everyone! I have made a first version of my proposal for GSoC project with Camel. Please take a look and give your comments. https://github.com/manonthegithub/GSoC-2020/blob/master/camel/Proposal.md <https://github.com/manonthegithub/GSoC-2020/blob/master/camel/Proposal.md> Looking f

Re: Re: Student Proposal Submission for GSOC 2019

> or Databases. >> > Or can someone help me with the APIs? >> > >> > Thanks, >> > Shikha >> > >> > >> > On Tue, Apr 9, 2019 at 11:32 PM Andrea Cosentino >> wrote: >> >> >> >> Go for it for me >&

Re: Re: Student Proposal Submission for GSOC 2019

; >> > >> Inviato da Yahoo Mail su Android > >> > >> Il mar, 9 apr, 2019 alle 19:59, Shikha Singh > >> <115shikha.si...@gmail.com> ha scritto: > >> Hi everyone, > >> Just a small reminder, as the last day for proposal submission

Re: Re: Student Proposal Submission for GSOC 2019

9 apr, 2019 alle 19:59, Shikha Singh >> <115shikha.si...@gmail.com> ha scritto: >> Hi everyone, >> Just a small reminder, as the last day for proposal submission is day >> after tomorrow. >> Just wanted to confirm once again, should I go with this one, any commen

Re: Re: Student Proposal Submission for GSOC 2019

//go.onelink.me/107872968?pid=InProduct=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature> > > Il mar, 9 apr, 2019 alle 19:59, Shikha Singh > <115shikha.si...@gmail.com> ha scritto: > Hi everyone, > Just a small

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

> > > > > > > > > > > Hi Willem. > > > > > > > > > > > > Thanks so much. It would be great if you can help me as my mentor. > > > > > > Currently, I have been trying to work on some Jira issues in order >

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

as my mentor. > > > > > Currently, I have been trying to work on some Jira issues in order > to > > > > > understand better Camel. I have being trying to reproduce [1] and > > come > > > up > > > > > with a solution. > > > > &g

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

nd better Camel. I have being trying to reproduce [1] and > come > > up > > > > with a solution. > > > > > > > > Please let me know if you have further suggestions on how I can > better > > > > take adventage of the bonding period. > > &

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

me know if you have further suggestions on how I can better > > > take adventage of the bonding period. > > > > > > Also, I would like to know how to get in touch with you for planning > the > > > project during the coding period. > > > > > &g

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

get in touch with you for planning the > > project during the coding period. > > > > [1] https://issues.apache.org/jira/browse/CAMEL-13483 > > > > Best, > > Roberto > > > > > > El mar., 14 de may. de 2019 a la(s) 03:28, Willem Jiang (

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

ing the coding period. > > [1] https://issues.apache.org/jira/browse/CAMEL-13483 > > Best, > Roberto > > > El mar., 14 de may. de 2019 a la(s) 03:28, Willem Jiang ( > willem.ji...@gmail.com) escribió: > >> It's great to hear that you proposal was accepted. >> Did

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

...@gmail.com) escribió: > It's great to hear that you proposal was accepted. > Did you have chance to discuss the detail with your mentor? > If you need to find a mentor I'd happy to help you. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, May

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

It's great to hear that you proposal was accepted. Did you have chance to discuss the detail with your mentor? If you need to find a mentor I'd happy to help you. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, May 7, 2019 at 5:22 AM Beto Flores wrote: > > Hi all. > >

Fwd: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

Hi all. I have just received an email from the GSoC 2019 program and my proposal have been accepted. Thanks so much you guys for all your support during the application period and really hope that this summer will be productive working with the Apache Camel Community. Please let me know if you

R: Re: Student Proposal Submission for GSOC 2019

Go for it for me Inviato da Yahoo Mail su Android Il mar, 9 apr, 2019 alle 19:59, Shikha Singh<115shikha.si...@gmail.com> ha scritto: Hi everyone, Just a small reminder, as the last day for proposal submission is day after tomorrow. Just wanted to confirm once again, shoul

Re: Student Proposal Submission for GSOC 2019

Hi everyone, Just a small reminder, as the last day for proposal submission is day after tomorrow. Just wanted to confirm once again, should I go with this one, any comments are welcome. Thank you. On Wed, Apr 3, 2019 at 4:11 PM Andrea Cosentino wrote: > Looks really good. Tha

Re: [GoSC 2019 Proposal ] CAMEL-9260- Dataformat Apache Any23

Hi. Sorry for the noise. Thanks for your time, I understand that you are busy people. I am definitely still interested in the issue and I will continue playing with Camel and improving my proposal. Thanks, Roberto El mié., 3 de abr. de 2019 a la(s) 02:38, Zoran Regvart (zo...@regvart.com

R: Student Proposal Submission for GSOC 2019

https://issues.apache.org/jira/browse/CAMEL-12854 I have drafted my proposal and have followed the Application Template provided by The Apache Software Foundation. Sharing the proposal with you all and would be happy to recieve any reviews and suggestions from you all. https://docs.google.com/docu

Student Proposal Submission for GSOC 2019

Hi everyone, I am Shikha Singh and I am intersted to participate in GSOC 2019. I have decided to work on the issue - https://issues.apache.org/jira/browse/CAMEL-12854 I have drafted my proposal and have followed the Application Template provided by The Apache Software Foundation. Sharing

Re: [GoSC 2019 Proposal ] CAMEL-9260- Dataformat Apache Any23

Hi Roberto, I'm participating this years GSoC as one of the mentors, I apologize for not replying sooner to your proposal. Your proposal for GSoC is very good, I'm looking forward to your participation in the GSoC and your contribution to Apache Camel :) thank you :) zoran On Wed, Apr 3, 2019

R: Re: [GoSC 2019 Proposal ] CAMEL-9260- Dataformat Apache Any23

: Hi. I was wondering if you keep your interest on CAMEL-9260 [1] as a GSoC project. Since I have not received any reply to my proposal, I would like to know if I should look for other projects instead. Thanks, Roberto [1] https://issues.apache.org/jira/browse/CAMEL-9260 El mié., 27 de mar

Re: [GoSC 2019 Proposal ] CAMEL-9260- Dataformat Apache Any23

Hi. I was wondering if you keep your interest on CAMEL-9260 [1] as a GSoC project. Since I have not received any reply to my proposal, I would like to know if I should look for other projects instead. Thanks, Roberto [1] https://issues.apache.org/jira/browse/CAMEL-9260 El mié., 27 de mar. de

R: Re: Student proposal submission for GSOC 2019.

to improve my proposal for GSoC 2019. I have resolved all the pointed issues except scheduling. I Still didn`t share this proposal with Apache Software Foundation. I think now it is considerably good to share this draft with the Apache Software Foundation. I would like to ask your opinions regarding

Re: Student proposal submission for GSOC 2019.

Hi everyone, I really appreciate Mr.Zoran, Miss Andrea and Mr.Jason effort to improve my proposal for GSoC 2019. I have resolved all the pointed issues except scheduling. I Still didn`t share this proposal with Apache Software Foundation. I think now it is considerably good to share this draft

[GoSC 2019 Proposal ] CAMEL-9260- Dataformat Apache Any23

Hi everyone. I am Roberto Flores, a Computer Science student at University of Cuenca and I would like to participate in the Google Summer of Code program. I am especially interested in the CAMEL-9260- Dataformat Apache Any23[1] issue, so I have created a first draft of my proposal. https

Re: Student proposal submission for GSOC 2019.

, Zoran Regvart wrote: Hi Nayananga, thank you for creating this, I left a few comments, perhaps other mentors can have a look. zoran On Tue, Mar 26, 2019 at 7:11 PM Nayananga Muhandiram wrote: > > Hi everyone, Since GSOC 2019 student proposal submission is open I have > drafted my

Re: Student proposal submission for GSOC 2019.

Hi Nayananga, thank you for creating this, I left a few comments, perhaps other mentors can have a look. zoran On Tue, Mar 26, 2019 at 7:11 PM Nayananga Muhandiram wrote: > > Hi everyone, Since GSOC 2019 student proposal submission is open I have > drafted my proposal. I would like t

Student proposal submission for GSOC 2019.

Hi everyone, Since GSOC 2019 student proposal submission is open I have drafted my proposal. I would like to receive comments and thoughts in order to improve it to an ultra possible acceptance level. Please help me to submit a good proposal and get selected to contribute to this project as my

[GitHub] zregvart closed pull request #3: [CAMEL-12998] Website design proposal

zregvart closed pull request #3: [CAMEL-12998] Website design proposal URL: https://github.com/apache/camel-website/pull/3 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull

[GitHub] fpapon opened a new pull request #3: [CAMEL-12998] Website design proposal

fpapon opened a new pull request #3: [CAMEL-12998] Website design proposal URL: https://github.com/apache/camel-website/pull/3 This is a first round about website design proposal. This is an automated message from the Apache

Re: [PROPOSAL] Setting up an official ASF swag store

Hello, I'm a committer and a PMC member of Apache Camel project. I've made a handful of Apache Camel branded T-shirts that I gave to my colleagues and I'll also give away some tomorrow at EU Roadshow. Having been contacted by a community member wishing to purchase these and never intending to

[GitHub] camel pull request #2198: CAMEL-12209: Proposal to fix by adding an overload

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2198 ---

[GitHub] camel pull request #2198: CAMEL-12209: Proposal to fix by adding an overload

GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/2198 CAMEL-12209: Proposal to fix by adding an overload Please check [CAMEL-12209](https://issues.apache.org/jira/browse/CAMEL-12209) out for more details. You can merge this pull request

[GitHub] camel pull request #1804: CAMEL-11511: Proposal to enhance the `BeanInfo` in...

Github user aldettinger closed the pull request at: https://github.com/apache/camel/pull/1804 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] camel pull request #1804: CAMEL-11511: Proposal to enhance the `BeanInfo` in...

GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/1804 CAMEL-11511: Proposal to enhance the `BeanInfo` introspection in 2 cases Proposal to enhance the `BeanInfo` introspection in 2 cases: - A package private class implementing a 2 hop interface

[GitHub] camel pull request #1703: CAMEL-11235: Proposal to fix an issue where a meth...

Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1703 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] camel pull request #1703: CAMEL-11235: Proposal to fix an issue where a meth...

GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/1703 CAMEL-11235: Proposal to fix an issue where a method inherited from a superclass overrides a superinterface method This PR proposes a fix for [CAMEL-11235](https://issues.apache.org/jira

Re: [PROPOSAL] camel-extra moves forward

On 09/06/15 14:54, Christoph Emmersberger wrote: Ok, ... so I'll run the release now off the old Google Code repositories. Can anybody cross check if I have the appropriate rights on the GitHub repository to commit tags? I've given it quite a few shots and it still won't let me prepare the

Re: [PROPOSAL] camel-extra moves forward

Hello Christian! Thanks for the update! / Christoph On Sat, Jul 4, 2015 at 6:27 AM, Christian Müller christian.muel...@gmail.com wrote: Hello Christoph! Once again, I encourage you (and all other Apache-Extra developers) to subscribe to the Apache community development mailing list [1]

Re: [PROPOSAL] camel-extra moves forward

Hello Christoph! Once again, I encourage you (and all other Apache-Extra developers) to subscribe to the Apache community development mailing list [1] and follow/discuss your opinions in the Apache Extras, Google Code and Sourceforge thread [3]. Unfortunately (my personal view), it looks like

Re: [PROPOSAL] camel-extra moves forward

Hi Christian As August is approaching, and Greg has already put some effort into migrating the project to GitHub, I'd like to reach out once again. Did you hear any official statement on how to proceed after August? I also heard some rumors that Google might be creating another hosting

Re: [PROPOSAL] camel-extra moves forward

Ok, ... so I'll run the release now off the old Google Code repositories. Can anybody cross check if I have the appropriate rights on the GitHub repository to commit tags? I've given it quite a few shots and it still won't let me prepare the release from there. Just wanted to make sure we are in

Re: [PROPOSAL] camel-extra moves forward

Hi Pontus, For now, commit only to Google Code. Cheers. wt., 28.04.2015 o 09:05 użytkownik Pontus Ullgren ullg...@gmail.com napisał: Pressed send a bit fast there sorry. I'm planning to have a look at CAMEX-61[1] today and it would be nice to know where it should be committed. [1]

Re: [PROPOSAL] camel-extra moves forward

Pressed send a bit fast there sorry. I'm planning to have a look at CAMEX-61[1] today and it would be nice to know where it should be committed. [1] https://camel-extra.atlassian.net/browse/CAMEX-61 On Tue, 28 Apr 2015 at 09:00 Pontus Ullgren ullg...@gmail.com wrote: Think I already voted in

Re: [PROPOSAL] camel-extra moves forward

Github is more popular now days, +1 for moving camel-extra to Github. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On April 27, 2015 at 2:13:01 AM, Christian

Re: [PROPOSAL] Move camel-extra from google code to github ?

Sent from webmail - Mail original - De: Krzysztof Sobkowiak À: dev@camel.apache.org Envoyé: Samedi 11 Avril 2015 15:41:47 Objet: Re: [PROPOSAL] Move camel-extra from google code to github ? Hi I think Github

Re: [PROPOSAL] Move camel-extra from google code to github ?

I also reserved a 'apache-extra' organization name if we might need one, figured that 'apache-extras' was already occupied.

  1   2   >