[GitHub] kameshsampath opened a new issue #497: Upgrade to Knative > v0.3.0

kameshsampath opened a new issue #497: Upgrade to Knative > v0.3.0 URL: https://github.com/apache/camel-k/issues/497 As knative v0.4.0 its out, it is better to have the camel-k apis upgraded to use minimum v0.3.0 of Knative API. It will be nicer if v0.4.0 is done as there some new f

[GitHub] kameshsampath closed issue #497: Upgrade to Knative > v0.3.0

kameshsampath closed issue #497: Upgrade to Knative > v0.3.0 URL: https://github.com/apache/camel-k/issues/497 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] kameshsampath opened a new issue #497: Upgrade to Knative v0.3.0

kameshsampath opened a new issue #497: Upgrade to Knative v0.3.0 URL: https://github.com/apache/camel-k/issues/497 As knative v0.4.0 its out, it is better to have the camel-k apis upgraded to use minimum v0.3.0 of Knative API. It will be nicer if v0.4.0 is done as there some new feat

[GitHub] marcredhat opened a new issue #493: camel-k on Openshift Container Platform 3.11

marcredhat opened a new issue #493: camel-k on Openshift Container Platform 3.11 URL: https://github.com/apache/camel-k/issues/493 I set up camel-k on Openshift Enterprise 3.11.59 Works like a charm (see https://bit.ly/2Nrieca) but some of the steps below were not obvious (to me). The

[GitHub] marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11

marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11 URL: https://github.com/apache/camel-k/issues/493#issuecomment-467067914 This is how I deployed OCP 3.11: https://github.com/marcredhat/openshiftonhyperv/commit/9b4975927366e0fe6e4620eb9244171239740ec7 ---

[GitHub] marcredhat closed issue #493: camel-k on Openshift Container Platform 3.11

marcredhat closed issue #493: camel-k on Openshift Container Platform 3.11 URL: https://github.com/apache/camel-k/issues/493 This is an automated message from the Apache Git Service. To respond to the message, please log on G

[GitHub] marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11

marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11 URL: https://github.com/apache/camel-k/issues/493#issuecomment-467066097 Sure: oc get integrationplatform -o yaml apiVersion: v1 items: - apiVersion: camel.apache.org/v1alpha1 kind: IntegrationP

[GitHub] lburgazzoli closed issue #468: do not include runtime artefacts in operator image by default

lburgazzoli closed issue #468: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/issues/468 This is an automated message from the Apache Git Service. To respond to the messa

[GitHub] lburgazzoli commented on issue #490: Came-k routes takes long time to terminate

lburgazzoli commented on issue #490: Came-k routes takes long time to terminate URL: https://github.com/apache/camel-k/issues/490#issuecomment-467052928 fixed by #496 This is an automated message from the Apache Git Service.

[GitHub] lburgazzoli commented on issue #468: do not include runtime artefacts in operator image by default

lburgazzoli commented on issue #468: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/issues/468#issuecomment-467053309 Fixed by #486 This is an automated message from the

[GitHub] lburgazzoli closed issue #490: Came-k routes takes long time to terminate

lburgazzoli closed issue #490: Came-k routes takes long time to terminate URL: https://github.com/apache/camel-k/issues/490 This is an automated message from the Apache Git Service. To respond to the message, please log on Gi

[GitHub] lburgazzoli merged pull request #486: do not include runtime artefacts in operator image by default

lburgazzoli merged pull request #486: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/pull/486 This is an automated message from the Apache Git Service. To respond to the

[GitHub] lburgazzoli closed issue #487: improve resource gc performances

lburgazzoli closed issue #487: improve resource gc performances URL: https://github.com/apache/camel-k/issues/487 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and u

[GitHub] lburgazzoli merged pull request #496: Perform garbage collection asynchronously

lburgazzoli merged pull request #496: Perform garbage collection asynchronously URL: https://github.com/apache/camel-k/pull/496 This is an automated message from the Apache Git Service. To respond to the message, please log o

Re: maven plugin in 3.0.0-M1

By the way, this was reported in Migration guide in the  Migrating Camel Maven Plugins section -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On

Re: maven plugin in 3.0.0-M1

No problem, and thanks for checking the M1. It's not easy to track everything on the Migration Guide, so this kind of informations are always good. Thanks a lot for the help! -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix

Re: maven plugin in 3.0.0-M1

Ah. Sorry for not catching that. Den man. 25. feb. 2019, 15:48 skrev Andrea Cosentino : > By the way, this was reported in Migration guide in the > > Migrating Camel Maven Plugins section > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Commit

[GitHub] astefanutti commented on a change in pull request #496: Perform garbage collection asynchronously

astefanutti commented on a change in pull request #496: Perform garbage collection asynchronously URL: https://github.com/apache/camel-k/pull/496#discussion_r259840131 ## File path: pkg/trait/gc.go ## @@ -72,36 +74,47 @@ func (t *garbageCollectorTrait) Apply(e *Environment

[GitHub] lburgazzoli commented on a change in pull request #496: Perform garbage collection asynchronously

lburgazzoli commented on a change in pull request #496: Perform garbage collection asynchronously URL: https://github.com/apache/camel-k/pull/496#discussion_r259823945 ## File path: pkg/trait/gc.go ## @@ -72,36 +74,47 @@ func (t *garbageCollectorTrait) Apply(e *Environment

[GitHub] nicolaferraro commented on issue #493: camel-k on Openshift Container Platform 3.11

nicolaferraro commented on issue #493: camel-k on Openshift Container Platform 3.11 URL: https://github.com/apache/camel-k/issues/493#issuecomment-467010800 I've not tried it on Openshift Enterprise, but I assume it ships with S2I and a namespaced imagestream registry where S2I pushes imag

[GitHub] astefanutti opened a new pull request #496: Perform garbage collection asynchronously

astefanutti opened a new pull request #496: Perform garbage collection asynchronously URL: https://github.com/apache/camel-k/pull/496 Fixes #487 This is an automated message from the Apache Git Service. To respond to the mess

[GitHub] lburgazzoli commented on issue #486: do not include runtime artefacts in operator image by default

lburgazzoli commented on issue #486: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/pull/486#issuecomment-467010126 so let see how may thing we'll break This is an automat

[GitHub] lburgazzoli commented on a change in pull request #486: do not include runtime artefacts in operator image by default

lburgazzoli commented on a change in pull request #486: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/pull/486#discussion_r259820418 ## File path: script/Makefile ## @@ -1,8 +1,55 @@ -build: build-runtime build-operato

[GitHub] nicolaferraro commented on a change in pull request #486: do not include runtime artefacts in operator image by default

nicolaferraro commented on a change in pull request #486: do not include runtime artefacts in operator image by default URL: https://github.com/apache/camel-k/pull/486#discussion_r259817905 ## File path: script/Makefile ## @@ -1,8 +1,55 @@ -build: build-runtime build-opera

[GitHub] kameshsampath opened a new issue #495: Minimum Kubernetes version

kameshsampath opened a new issue #495: Minimum Kubernetes version URL: https://github.com/apache/camel-k/issues/495 Due to a bug with CoreDNS that is shipped for mac and minikube iso ref: https://github.com/knative/serving/issues/3067 its worth updating the documentation for minimum k8s ve

[GitHub] kameshsampath edited a comment on issue #483: Unable to send message to knative channel

kameshsampath edited a comment on issue #483: Unable to send message to knative channel URL: https://github.com/apache/camel-k/issues/483#issuecomment-467003540 It was bug with CoreDNS on kubernetes v1.11.0 on **minikube**., it got resolved upgrading minikube to v1.12.0. Ref: https

[GitHub] kameshsampath closed issue #483: Unable to send message to knative channel

kameshsampath closed issue #483: Unable to send message to knative channel URL: https://github.com/apache/camel-k/issues/483 This is an automated message from the Apache Git Service. To respond to the message, please log on G

[GitHub] kameshsampath commented on issue #483: Unable to send message to knative channel

kameshsampath commented on issue #483: Unable to send message to knative channel URL: https://github.com/apache/camel-k/issues/483#issuecomment-467003540 It was bug with CoreDNS on kubernetes v1.11.0 on **minikube**., it got resolved upgrading minikube to v1.12.0.

Re: maven plugin in 3.0.0-M1

That Mojo should now be in camel-report-maven-plugin Thanks for spotting this, I'll add this to the migration guide .adoc file -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @

[GitHub] oscerd merged pull request #16: Support for camel 3.x

oscerd merged pull request #16: Support for camel 3.x URL: https://github.com/apache/camel-k-runtime/pull/16 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use th

[GitHub] oscerd closed issue #11: Support for camel 3.x

oscerd closed issue #11: Support for camel 3.x URL: https://github.com/apache/camel-k-runtime/issues/11 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL

Re: maven plugin in 3.0.0-M1

This one: org.apache.camel camel-maven-plugin Den man. 25. feb. 2019 kl. 13:41 skrev Andrea Cosentino < ancosen1...@yahoo.com>: > What maven plugin? > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > E

Re: maven plugin in 3.0.0-M1

What maven plugin? -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, February 25, 2019, 1:20:22 PM GMT+1, David Karlsen wrote: The

[GitHub] lburgazzoli opened a new issue #17: Release 0.3.0

lburgazzoli opened a new issue #17: Release 0.3.0 URL: https://github.com/apache/camel-k-runtime/issues/17 We need to release version 0.3.0 - [ ] support for camel 3.x This is an automated message from the Apach

[GitHub] lburgazzoli opened a new pull request #16: Support for camel 3.x

lburgazzoli opened a new pull request #16: Support for camel 3.x URL: https://github.com/apache/camel-k-runtime/pull/16 Initial support for camel 3.0.0-M1 Fixes #11 This is an automated message from the Apache Git Servi

maven plugin in 3.0.0-M1

The validation goal seems to have been removed in this version of the plugin - I could not find any docs on it - could someone shed some light on this? -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[GitHub] lburgazzoli merged pull request #491: sanitize dependencies

lburgazzoli merged pull request #491: sanitize dependencies URL: https://github.com/apache/camel-k/pull/491 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the

[GitHub] astefanutti merged pull request #494: Do not swallow error returned by controller actions

astefanutti merged pull request #494: Do not swallow error returned by controller actions URL: https://github.com/apache/camel-k/pull/494 This is an automated message from the Apache Git Service. To respond to the message, p

[GitHub] oscerd closed issue #14: Camel-k-runtime-merge job is failing

oscerd closed issue #14: Camel-k-runtime-merge job is failing URL: https://github.com/apache/camel-k-runtime/issues/14 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] oscerd merged pull request #15: fix(deploy): Camel-k-runtime-merge job is failing, fixes #14

oscerd merged pull request #15: fix(deploy): Camel-k-runtime-merge job is failing, fixes #14 URL: https://github.com/apache/camel-k-runtime/pull/15 This is an automated message from the Apache Git Service. To respond to the

[GitHub] oscerd opened a new pull request #15: fix(deploy): Camel-k-runtime-merge job is failing, fixes #14

oscerd opened a new pull request #15: fix(deploy): Camel-k-runtime-merge job is failing, fixes #14 URL: https://github.com/apache/camel-k-runtime/pull/15 This is an automated message from the Apache Git Service. To respond t

[GitHub] astefanutti opened a new pull request #494: Do not swallow error returned by controller actions

astefanutti opened a new pull request #494: Do not swallow error returned by controller actions URL: https://github.com/apache/camel-k/pull/494 This is an automated message from the Apache Git Service. To respond to the mess

[GitHub] oscerd opened a new issue #14: Camel-k-runtime-merge job is failing

oscerd opened a new issue #14: Camel-k-runtime-merge job is failing URL: https://github.com/apache/camel-k-runtime/issues/14 https://builds.apache.org/view/C/view/Apache%20Camel/job/camel-k-merge/39/console This is an automat

[GitHub] astefanutti commented on issue #487: improve resource gc performances

astefanutti commented on issue #487: improve resource gc performances URL: https://github.com/apache/camel-k/issues/487#issuecomment-466920822 One option may be to change the delete operation options to either use a `background` or `orphan` propagation policy. If that does not lead to a si