[GitHub] lburgazzoli opened a new pull request #343: builder: add hooks to the builder state changes to update resources when the build completes

2019-01-18 Thread GitBox
lburgazzoli opened a new pull request #343: builder: add hooks to the builder state changes to update resources when the build completes URL: https://github.com/apache/camel-k/pull/343 With this PR I have refactored the builder so we can add event handlers and react to build state change

[GitHub] lburgazzoli commented on issue #342: platform: wait for context to be ready before installing next context

2019-01-18 Thread GitBox
lburgazzoli commented on issue #342: platform: wait for context to be ready before installing next context URL: https://github.com/apache/camel-k/pull/342#issuecomment-455588575 let me think about another solution This is an

[GitHub] lburgazzoli closed pull request #342: platform: wait for context to be ready before installing next context

2019-01-18 Thread GitBox
lburgazzoli closed pull request #342: platform: wait for context to be ready before installing next context URL: https://github.com/apache/camel-k/pull/342 This is an automated message from the Apache Git Service. To respond

[GitHub] nicolaferraro commented on issue #342: platform: wait for context to be ready before installing next context

2019-01-18 Thread GitBox
nicolaferraro commented on issue #342: platform: wait for context to be ready before installing next context URL: https://github.com/apache/camel-k/pull/342#issuecomment-455584937 Ok, but I think it blocks the controller goroutine and events will keep accumulating.. --

[GitHub] lburgazzoli commented on issue #342: platform: wait for context to be ready before installing next context

2019-01-18 Thread GitBox
lburgazzoli commented on issue #342: platform: wait for context to be ready before installing next context URL: https://github.com/apache/camel-k/pull/342#issuecomment-455583758 You'll wait only with `kamel install --wait`, otherwise the command exists. The platform create handler will

[GitHub] nicolaferraro commented on issue #342: platform: wait for context to be ready before installing next context

2019-01-18 Thread GitBox
nicolaferraro commented on issue #342: platform: wait for context to be ready before installing next context URL: https://github.com/apache/camel-k/pull/342#issuecomment-455575909 Not sure.. tehcnically when you don `kamel install` now you exit when the resources are created, you don't wai

[GitHub] nicolaferraro merged pull request #341: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
nicolaferraro merged pull request #341: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/pull/341 This is an automated message from the Apache Git Service. To respond to the m

[GitHub] nicolaferraro closed issue #340: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
nicolaferraro closed issue #340: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/issues/340 This is an automated message from the Apache Git Service. To respond to the messag

[GitHub] lburgazzoli opened a new pull request #341: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
lburgazzoli opened a new pull request #341: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/pull/341 Fixes #340 This is an automated message from the Apache Git Service. To re

[GitHub] lburgazzoli commented on issue #340: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
lburgazzoli commented on issue #340: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/issues/340#issuecomment-455545570 yes, it is part of the platform-cr.yaml This is an auto

[GitHub] nicolaferraro commented on issue #340: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
nicolaferraro commented on issue #340: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/issues/340#issuecomment-455544894 Maybe we can make it configurable at build time? So a build pipeline can override it if needed...

[GitHub] lburgazzoli opened a new issue #340: Allow to configure the base image used to run integrations

2019-01-18 Thread GitBox
lburgazzoli opened a new issue #340: Allow to configure the base image used to run integrations URL: https://github.com/apache/camel-k/issues/340 We do have `fabric8/s2i-java:2.3` hard coded into the sources, we should make it configurable at platform and integration level ---

[GitHub] oscerd merged pull request #339: Upgrade Jackson to version 2.9.8

2019-01-18 Thread GitBox
oscerd merged pull request #339: Upgrade Jackson to version 2.9.8 URL: https://github.com/apache/camel-k/pull/339 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and u

[GitHub] oscerd opened a new pull request #339: Upgrade Jackson to version 2.9.8

2019-01-18 Thread GitBox
oscerd opened a new pull request #339: Upgrade Jackson to version 2.9.8 URL: https://github.com/apache/camel-k/pull/339 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] lburgazzoli merged pull request #336: Some Knative improvements

2019-01-18 Thread GitBox
lburgazzoli merged pull request #336: Some Knative improvements URL: https://github.com/apache/camel-k/pull/336 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] lburgazzoli closed issue #324: Use standard deployment for Knative event sources

2019-01-18 Thread GitBox
lburgazzoli closed issue #324: Use standard deployment for Knative event sources URL: https://github.com/apache/camel-k/issues/324 This is an automated message from the Apache Git Service. To respond to the message, please lo

[GitHub] lburgazzoli closed issue #305: Allow to customize integration service account

2019-01-18 Thread GitBox
lburgazzoli closed issue #305: Allow to customize integration service account URL: https://github.com/apache/camel-k/issues/305 This is an automated message from the Apache Git Service. To respond to the message, please log o

[GitHub] lburgazzoli opened a new issue #338: VSCode extension

2019-01-18 Thread GitBox
lburgazzoli opened a new issue #338: VSCode extension URL: https://github.com/apache/camel-k/issues/338 Would be nice to have a VSCode extension that: - shows available integrations - edit integrations - show logs Some experimental work related to a camel-k ui from @ricca

Re: [ANNOUNCEMENT] Apache Camel 2.23.1 Released

2019-01-18 Thread Gregor Zurowski
Yes, the links in sections "API breaking" and "Known issues" are always pointing to the major/minor version, hence version 2.23.0 in this case. Thanks, Gregor On Fri, Jan 18, 2019 at 9:33 AM David Karlsen wrote: > > There are some 2.23.0 links on > http://camel.apache.org/camel-2231-release.html

Re: [ANNOUNCEMENT] Apache Camel 2.23.1 Released

2019-01-18 Thread David Karlsen
There are some 2.23.0 links on http://camel.apache.org/camel-2231-release.html Den fre. 18. jan. 2019 kl. 08:55 skrev Gregor Zurowski < gre...@list.zurowski.org>: > The Camel community announces the immediate availability of the Camel > 2.23.1 patch release. This release contains 33 fixes and imp

[GitHub] oscerd merged pull request #337: Bump to Camel 2.23.1

2019-01-18 Thread GitBox
oscerd merged pull request #337: Bump to Camel 2.23.1 URL: https://github.com/apache/camel-k/pull/337 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL a

Re: Release Camel 2.22.3

2019-01-18 Thread Claus Ibsen
+1 that would be good, then we have fresh set of patches out for all our active branches. On Fri, Jan 18, 2019 at 9:10 AM Gregor Zurowski wrote: > > Hi Everyone: > > We released the last patch version 2.22.2 for the Camel 2.22.x on > November 1st. In the meantime, 42 issues have been resolved on

Re: Release Camel 2.22.3

2019-01-18 Thread Andrea Cosentino
Hello Gregor, Yes, you're right. +1 Thanks a lot! -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, January 18, 2019, 9:10:20 AM GMT+1,

Release Camel 2.22.3

2019-01-18 Thread Gregor Zurowski
Hi Everyone: We released the last patch version 2.22.2 for the Camel 2.22.x on November 1st. In the meantime, 42 issues have been resolved on the camel-2.22.x branch: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344398&styleName=Text&projectId=12311211&Create=Create&atl_token=

[GitHub] oscerd opened a new pull request #337: Bump to Camel 2.23.1

2019-01-18 Thread GitBox
oscerd opened a new pull request #337: Bump to Camel 2.23.1 URL: https://github.com/apache/camel-k/pull/337 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the

[GitHub] oscerd closed pull request #337: Bump to Camel 2.23.1

2019-01-18 Thread GitBox
oscerd closed pull request #337: Bump to Camel 2.23.1 URL: https://github.com/apache/camel-k/pull/337 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL a

[GitHub] oscerd commented on issue #337: Bump to Camel 2.23.1

2019-01-18 Thread GitBox
oscerd commented on issue #337: Bump to Camel 2.23.1 URL: https://github.com/apache/camel-k/pull/337#issuecomment-455459661 retest this please This is an automated message from the Apache Git Service. To respond to the message