[GitHub] [camel-quarkus] ppalaga commented on issue #203: Release 0.2.0

ppalaga commented on issue #203: Release 0.2.0 URL: https://github.com/apache/camel-quarkus/issues/203#issuecomment-532569772 Thanks for the heads up, I can have a look tomorrow (on PTO today). This is an automated message

[GitHub] [camel-quarkus] oscerd commented on issue #203: Release 0.2.0

oscerd commented on issue #203: Release 0.2.0 URL: https://github.com/apache/camel-quarkus/issues/203#issuecomment-532563502 Release process was failing for failIfNoTests missing for surefire and now [INFO] [ERROR] Failed to execute goal

[GitHub] [camel-quarkus] oscerd commented on issue #203: Release 0.2.0

oscerd commented on issue #203: Release 0.2.0 URL: https://github.com/apache/camel-quarkus/issues/203#issuecomment-532565363 @ppalaga FYI. This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [camel-k] nicolaferraro opened a new pull request #940: Making kamel CLI 90% faster on remote clusters

nicolaferraro opened a new pull request #940: Making kamel CLI 90% faster on remote clusters URL: https://github.com/apache/camel-k/pull/940 Fix #792 Latest released version: ``` [nferraro@localhost camel-k]$ time kamel-1.0.0-M1 run examples/routes.groovy integration

[GitHub] [camel-k] utherp0 opened a new issue #941: kamel get still has a column for 'Context'

utherp0 opened a new issue #941: kamel get still has a column for 'Context' URL: https://github.com/apache/camel-k/issues/941 I might be confused but having read the renaming discussion and seen that the context command from Kamel has gone, it seems odd that 'kamel get' does this:

[GitHub] [camel-k-runtime] WillemJiang commented on issue #138: #137 Add the error log when setting component property failed

WillemJiang commented on issue #138: #137 Add the error log when setting component property failed URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-532718712 @lburgazzoli Could you take a look at my recent change?

[GitHub] [camel-k] bfitzpat commented on issue #938: Kamel cli should send exit code when integration in --dev mode is deleted

bfitzpat commented on issue #938: Kamel cli should send exit code when integration in --dev mode is deleted URL: https://github.com/apache/camel-k/issues/938#issuecomment-532797549 I eventually found a way round it. It turned out that the node.js child process "exec" call was creating a

[GitHub] [camel-k] nicolaferraro commented on issue #940: Making kamel CLI 90% faster on remote clusters

nicolaferraro commented on issue #940: Making kamel CLI 90% faster on remote clusters URL: https://github.com/apache/camel-k/pull/940#issuecomment-532871566 > Very useful when doing demos at conferences with bad wifi and clusters thousand kilometers away . You can call it

[GitHub] [camel-k] astefanutti closed issue #792: CLI too slow on remote clusters

astefanutti closed issue #792: CLI too slow on remote clusters URL: https://github.com/apache/camel-k/issues/792 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-k] astefanutti commented on issue #940: Making kamel CLI 90% faster on remote clusters

astefanutti commented on issue #940: Making kamel CLI 90% faster on remote clusters URL: https://github.com/apache/camel-k/pull/940#issuecomment-532816526 Very useful when doing demos at conferences with bad wifi and clusters thousand kilometers away .

[GitHub] [camel-k] astefanutti merged pull request #940: Making kamel CLI 90% faster on remote clusters

astefanutti merged pull request #940: Making kamel CLI 90% faster on remote clusters URL: https://github.com/apache/camel-k/pull/940 This is an automated message from the Apache Git Service. To respond to the message,