[GitHub] [camel-k] dmvolod commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

dmvolod commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582#issuecomment-477470715 Thanks for feedback. I will provide screens shortly. My situation is not so ordinal, but can b

[GitHub] [camel-k] dmvolod commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

dmvolod commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582#issuecomment-477470459 Thanks for feedback. I will provide screens shortly. My situation is not so ordinal, but can b

R: Re: Student proposal submission for GSOC 2019.

Yes, we can go ahead. Thanks. As a side note: I'm a Mr. In southern Europe Andrea is also a male name :-) Inviato da Yahoo Mail su Android Il mer, 27 mar, 2019 alle 18:59, Nayananga Muhandiram ha scritto: Hi everyone, I really appreciate Mr.Zoran, Miss Andrea and Mr.Jason effort to improv

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 with

[GitHub] [camel-k] lburgazzoli commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

lburgazzoli commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582#issuecomment-477273323 At the moment it is hard-coded but it tries five times with back-off then it stops --

[GitHub] [camel-k] nicolaferraro commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

nicolaferraro commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582#issuecomment-477271403 > As today it should move the context and the integration first to "build failure recovery" a

[GitHub] [camel-k] lburgazzoli commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

lburgazzoli commented on issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582#issuecomment-477261179 As today it should move the context and the integration first to "build failure recovery" and t

[GitHub] [camel-k] dmvolod opened a new issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails

dmvolod opened a new issue #582: camel-k-operator ready for running integration when camel-k-* builds are still fails URL: https://github.com/apache/camel-k/issues/582 Hi! The situation are very simple, for example one or more builds can not be run with Complete state and fails duri

[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://docs.g

[GitHub] [camel-k-runtime] lburgazzoli merged pull request #38: Need to exclude groovy-all here as well, possible for it to bleed in

lburgazzoli merged pull request #38: Need to exclude groovy-all here as well, possible for it to bleed in URL: https://github.com/apache/camel-k-runtime/pull/38 This is an automated message from the Apache Git Service. To re

[GitHub] [camel-k-runtime] cunningt commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in

cunningt commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in URL: https://github.com/apache/camel-k-runtime/pull/38#issuecomment-477213794 @lburgazzoli Added the wildcards - is there anything additional that needs to be added here?

[GitHub] [camel-k-runtime] cunningt commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in

cunningt commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in URL: https://github.com/apache/camel-k-runtime/pull/38#issuecomment-477162651 @lburgazzoli suggested using wildcards, so I've changed to excluding org.codehaus.groovy:* --

[GitHub] [camel-k-runtime] valdar commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in

valdar commented on issue #38: Need to exclude groovy-all here as well, possible for it to bleed in URL: https://github.com/apache/camel-k-runtime/pull/38#issuecomment-477156896 I think if you exclude it there you must add it as explicit dependency using `${groovy.vsersion}` version.

[GitHub] [camel-k-runtime] cunningt opened a new pull request #38: Need to exclude groovy-all here as well to satisfy PNC

cunningt opened a new pull request #38: Need to exclude groovy-all here as well to satisfy PNC URL: https://github.com/apache/camel-k-runtime/pull/38 Exclude groovy-all as well here This is an automated message from the Apach

Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

+1 (binding). Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 26, 2019 at 4:51 AM Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M2, the second milestone > towards a new 3.0.0 major release with currently 471 improvements and > fixes. > >

Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

+1 (non-binding) Thanks! Regards, François Papon fpa...@apache.org Le 26/03/2019 à 00:50, Gregor Zurowski a écrit : > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M2, the second milestone > towards a new 3.0.0 major release with currently 471 improvements and > fixes. > > Relea

[GitHub] [camel-k] astefanutti commented on issue #125: Split builder from operator

astefanutti commented on issue #125: Split builder from operator URL: https://github.com/apache/camel-k/issues/125#issuecomment-477054870 > That's nice. And it also helps with installation in Operator Hub. Exactly. It will remove the requirement for the persistent volume mount for th

[GitHub] [camel-k] nicolaferraro commented on issue #125: Split builder from operator

nicolaferraro commented on issue #125: Split builder from operator URL: https://github.com/apache/camel-k/issues/125#issuecomment-477053129 That's nice. And it also helps with installation in Operator Hub. This is an automated

Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

+1 Le lun. 25 mars 2019 à 21:51, Gregor Zurowski a écrit : > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M2, the second milestone > towards a new 3.0.0 major release with currently 471 improvements and > fixes. > > Release notes: > https://issues.apache.org/jira/secure/ReleaseN

Re: Student proposal submission for GSOC 2019.

I added a couple of comments too. Thanks Zoran -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, March 27, 2019, 9:22:24 AM GMT+1, Zor

Re: Getting Started

Hi Jason Great to hear from you. About tech and tools for building the new website then I have no preference. I am a noob in this regard. In terms of reaching out to us on chat etc, then I would actually suggest you to find us on gitter chat. Its easy as its just a web url and that is where we ha

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 to receive co

Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

+1 (binding) Thanks for the release Gregor, Alex On Wed, Mar 27, 2019 at 8:47 AM Zoran Regvart wrote: > +1 (binding) > > zoran > > On Mon, Mar 25, 2019 at 9:51 PM Gregor Zurowski > wrote: > > > > Hi Everyone: > > > > This is a vote to release Apache Camel 3.0.0-M2, the second milestone > > tow

Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

+1 (binding) zoran On Mon, Mar 25, 2019 at 9:51 PM Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M2, the second milestone > towards a new 3.0.0 major release with currently 471 improvements and > fixes. > > Release notes: > https://issues.apache.org/ji