[GitHub] [camel-quarkus] ppalaga opened a new pull request #26: Fix #25 Use the same naming scheme for artifactIds and module names

ppalaga opened a new pull request #26: Fix #25 Use the same naming scheme for artifactIds and module names URL: https://github.com/apache/camel-quarkus/pull/26 This is an automated message from the Apache Git Service. To res

[GitHub] [camel-quarkus] ppalaga commented on issue #26: Fix #25 Use the same naming scheme for artifactIds and module names

ppalaga commented on issue #26: Fix #25 Use the same naming scheme for artifactIds and module names URL: https://github.com/apache/camel-quarkus/pull/26#issuecomment-507791928 565898d has passed in my fork https://travis-ci.org/ppalaga/camel-quarkus/builds/553398728?utm_source=github_statu

[GitHub] [camel-quarkus] ppalaga opened a new pull request #27: Add badges and How to build section to the README

ppalaga opened a new pull request #27: Add badges and How to build section to the README URL: https://github.com/apache/camel-quarkus/pull/27 This is an automated message from the Apache Git Service. To respond to the messag

[GitHub] [camel-quarkus] davsclaus merged pull request #27: Add badges and How to build section to the README

davsclaus merged pull request #27: Add badges and How to build section to the README URL: https://github.com/apache/camel-quarkus/pull/27 This is an automated message from the Apache Git Service. To respond to the message, p

[GitHub] [camel-quarkus] davsclaus merged pull request #26: Fix #25 Use the same naming scheme for artifactIds and module names

davsclaus merged pull request #26: Fix #25 Use the same naming scheme for artifactIds and module names URL: https://github.com/apache/camel-quarkus/pull/26 This is an automated message from the Apache Git Service. To respond

[GitHub] [camel-quarkus] davsclaus closed issue #25: Rename integration test artifacts

davsclaus closed issue #25: Rename integration test artifacts URL: https://github.com/apache/camel-quarkus/issues/25 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-k-runtime] davsclaus merged pull request #89: Ass keys

davsclaus merged pull request #89: Ass keys URL: https://github.com/apache/camel-k-runtime/pull/89 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL a

[GitHub] [camel-k] lburgazzoli commented on issue #799: Move waiting for platform to controller

lburgazzoli commented on issue #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#issuecomment-507983746 @astefanutti this PR contains also a small fix for #784 where the integration was not moved to the runnig state --

[GitHub] [camel-k-runtime] oscerd merged pull request #90: Update dependencies

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

[GitHub] [camel-quarkus] lburgazzoli opened a new pull request #28: Avoid 3rd party maven repositories if possible

lburgazzoli opened a new pull request #28: Avoid 3rd party maven repositories if possible URL: https://github.com/apache/camel-quarkus/pull/28 Fixes #20 This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #29: Use docker-build in travis

lburgazzoli opened a new issue #29: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/issues/29 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHu

[GitHub] [camel-quarkus] lburgazzoli opened a new pull request #30: Use docker-build in travis

lburgazzoli opened a new pull request #30: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/pull/30 Fixes #29 This is an automated message from the Apache Git Service. To respond to the message, please l

[GitHub] [camel-quarkus] ppalaga commented on issue #28: Avoid 3rd party maven repositories if possible

ppalaga commented on issue #28: Avoid 3rd party maven repositories if possible URL: https://github.com/apache/camel-quarkus/pull/28#issuecomment-508008791 :thumbsup: This is an automated message from the Apache Git Service. To

[GitHub] [camel-quarkus] ppalaga commented on issue #30: Use docker-build in travis

ppalaga commented on issue #30: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/pull/30#issuecomment-508010176 The change in itself is OK (as long as it going to pass on Travis), but after the change, this piece of README that refers to `.travis.yml` got invalid: ht

[GitHub] [camel-quarkus] ppalaga edited a comment on issue #30: Use docker-build in travis

ppalaga edited a comment on issue #30: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/pull/30#issuecomment-508010176 The change in itself is OK (as long as it is going to pass on Travis), but after the change, this piece of README that refers to `.travis.yml` got i

[GitHub] [camel-quarkus] lburgazzoli commented on issue #30: Use docker-build in travis

lburgazzoli commented on issue #30: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/pull/30#issuecomment-508012390 @ppalaga fixed This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #31: Move infinispan tests out fo core

lburgazzoli opened a new issue #31: Move infinispan tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31 This is an automated message from the Apache Git Service. To respond to the message, please log on t

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #32: Move netty integration-tests out fo core

lburgazzoli opened a new issue #32: Move netty integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/32 This is an automated message from the Apache Git Service. To respond to the message, please l

[GitHub] [camel-quarkus] ppalaga commented on issue #31: Move infinispan integration-tests out fo core

ppalaga commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508017386 I clearly see the benefit of testing separately and having a separate project for each component that can serve as a basic quickstart.

[GitHub] [camel-quarkus] oscerd commented on issue #31: Move infinispan integration-tests out fo core

oscerd commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508018225 I think a reasonable time for CI can be more than 40 minutes. This is a

[GitHub] [camel-quarkus] ppalaga commented on issue #31: Move infinispan integration-tests out fo core

ppalaga commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508020731 > I think a reasonable time for CI can be more than 40 minutes. I wonder what is your upper bound for a CI job that verifies pull

[GitHub] [camel-quarkus] oscerd commented on issue #31: Move infinispan integration-tests out fo core

oscerd commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508021242 it depends on the dimension of a project: in camel we cannot do a full build because it's too much stuff for a single PR. I think up to

[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #31: Move infinispan integration-tests out fo core

lburgazzoli edited a comment on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508026975 > I clearly see the benefit of testing separately and having a separate project for each component that can serve as a basi

[GitHub] [camel-quarkus] lburgazzoli commented on issue #31: Move infinispan integration-tests out fo core

lburgazzoli commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508026975 > I clearly see the benefit of testing separately and having a separate project for each component that can serve as a basic quick

[GitHub] [camel-quarkus] lburgazzoli merged pull request #28: Avoid 3rd party maven repositories if possible

lburgazzoli merged pull request #28: Avoid 3rd party maven repositories if possible URL: https://github.com/apache/camel-quarkus/pull/28 This is an automated message from the Apache Git Service. To respond to the message, pl

[GitHub] [camel-quarkus] lburgazzoli closed issue #20: Avoid 3rd party maven repositories if possible

lburgazzoli closed issue #20: Avoid 3rd party maven repositories if possible URL: https://github.com/apache/camel-quarkus/issues/20 This is an automated message from the Apache Git Service. To respond to the message, please l

[GitHub] [camel-quarkus] ppalaga commented on issue #31: Move infinispan integration-tests out fo core

ppalaga commented on issue #31: Move infinispan integration-tests out fo core URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508030790 Yes, there is no doubt that more coverage is better. This is an automa

[GitHub] [camel-k] lburgazzoli commented on issue #762: Execute maven operation asynchronously

lburgazzoli commented on issue #762: Execute maven operation asynchronously URL: https://github.com/apache/camel-k/issues/762#issuecomment-508039255 we could something similar to what the "build" controller does This is an aut

[GitHub] [camel-k] lburgazzoli edited a comment on issue #762: Execute maven operation asynchronously

lburgazzoli edited a comment on issue #762: Execute maven operation asynchronously URL: https://github.com/apache/camel-k/issues/762#issuecomment-508039255 we could do something similar to what the "build" controller does. Th

[GitHub] [camel-quarkus] lburgazzoli closed issue #29: Use docker-build in travis

lburgazzoli closed issue #29: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/issues/29 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-quarkus] lburgazzoli merged pull request #30: Use docker-build in travis

lburgazzoli merged pull request #30: Use docker-build in travis URL: https://github.com/apache/camel-quarkus/pull/30 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #33: Move jetty processor from salesforce to a dedicated extension

lburgazzoli opened a new issue #33: Move jetty processor from salesforce to a dedicated extension URL: https://github.com/apache/camel-quarkus/issues/33 The main question is where ? as camel has also a camel-jetty component we can't put the jetty extension under the extension folder as the

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #34: Move XStream processor from salesforce to a dedicated extension

lburgazzoli opened a new issue #34: Move XStream processor from salesforce to a dedicated extension URL: https://github.com/apache/camel-quarkus/issues/34 The main question is where ? as camel has also a camel-xstream component we can't put the xstream extension under the extension folder

[GitHub] [camel-k] lburgazzoli opened a new pull request #800: Support for new yaml dsl

lburgazzoli opened a new pull request #800: Support for new yaml dsl URL: https://github.com/apache/camel-k/pull/800 Fixes #781 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [camel-quarkus] ppalaga commented on issue #24: "Multiple consumers for the same endpoint" after renaming packages in extensions/servlet/deployment/src/test/java

ppalaga commented on issue #24: "Multiple consumers for the same endpoint" after renaming packages in extensions/servlet/deployment/src/test/java URL: https://github.com/apache/camel-quarkus/issues/24#issuecomment-508110711 So given that the current PR is blocked by changes that need to get

[GitHub] [camel-k] astefanutti merged pull request #801: chore(build): strip full path from stackstraces

astefanutti merged pull request #801: chore(build): strip full path from stackstraces URL: https://github.com/apache/camel-k/pull/801 This is an automated message from the Apache Git Service. To respond to the message, pleas

[GitHub] [camel-k] lburgazzoli merged pull request #800: Support for new yaml dsl

lburgazzoli merged pull request #800: Support for new yaml dsl URL: https://github.com/apache/camel-k/pull/800 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and u

[GitHub] [camel-k] lburgazzoli closed issue #781: Support for new yaml dsl

lburgazzoli closed issue #781: Support for new yaml dsl URL: https://github.com/apache/camel-k/issues/781 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

[GitHub] [camel-quarkus] ppalaga commented on issue #8: quarkus-camel - Migrate option prefixes

ppalaga commented on issue #8: quarkus-camel - Migrate option prefixes URL: https://github.com/apache/camel-quarkus/issues/8#issuecomment-508272008 What is the motivation for this change? Asking because the property naming conventions are currently discussed on quarkus-dev ML [1] and we sho

[GitHub] [camel-k] jamesnetherton commented on issue #793: e2e tests are failing on travis

jamesnetherton commented on issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793#issuecomment-508354809 I've run over 30 test builds and not had any failures since Tuesday when Travis was super flaky (all kinds of random failures were occurring).

[GitHub] [camel-k] lburgazzoli commented on issue #793: e2e tests are failing on travis

lburgazzoli commented on issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793#issuecomment-508355639 let's try This is an automated message from the Apache Git Service. To respond to th

[GitHub] [camel-k] jamesnetherton opened a new pull request #802: chore: Re-enable e2e tests

jamesnetherton opened a new pull request #802: chore: Re-enable e2e tests URL: https://github.com/apache/camel-k/pull/802 fixes #793 This is an automated message from the Apache Git Service. To respond to the message, please l

[GitHub] [camel-k] jamesnetherton commented on issue #793: e2e tests are failing on travis

jamesnetherton commented on issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793#issuecomment-508358418 Since the Travis debug option isn't available on the main build, I was thinking it might be nice to enhance the e2e tests to try and capture the

[GitHub] [camel-k] lburgazzoli commented on issue #793: e2e tests are failing on travis

lburgazzoli commented on issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793#issuecomment-508359254 I've added a bunch of them here https://github.com/lburgazzoli/apache-camel-k/commits/e2e-timeout, if it can help. But they were just attempt, not a

[GitHub] [camel-k] lburgazzoli closed issue #793: e2e tests are failing on travis

lburgazzoli closed issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-k] lburgazzoli merged pull request #802: chore: Re-enable e2e tests

lburgazzoli merged pull request #802: chore: Re-enable e2e tests URL: https://github.com/apache/camel-k/pull/802 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-quarkus] lburgazzoli commented on issue #8: quarkus-camel - Migrate option prefixes

lburgazzoli commented on issue #8: quarkus-camel - Migrate option prefixes URL: https://github.com/apache/camel-quarkus/issues/8#issuecomment-508375830 I think that for extension related properties - so those that influence the build phase - we should keep the `quarkus.camel` prefix, for ca

[GitHub] [camel-quarkus] davsclaus commented on issue #7: Upgrade to Camel SNAPSHOT

davsclaus commented on issue #7: Upgrade to Camel SNAPSHOT URL: https://github.com/apache/camel-quarkus/issues/7#issuecomment-508376513 Okay yeah we can have it by default use a released version of Camel, but we should have an easy way to build with camel SNAPSHOT version, maybe like a mav

[GitHub] [camel-quarkus] davsclaus commented on issue #7: Upgrade to Camel SNAPSHOT

davsclaus commented on issue #7: Upgrade to Camel SNAPSHOT URL: https://github.com/apache/camel-quarkus/issues/7#issuecomment-508376600 Especially now when we need to upgrade from M2 to M4 This is an automated message from the

[GitHub] [camel-quarkus] davsclaus commented on issue #8: quarkus-camel - Migrate option prefixes

davsclaus commented on issue #8: quarkus-camel - Migrate option prefixes URL: https://github.com/apache/camel-quarkus/issues/8#issuecomment-508377364 Yeah what Luca says is good, that some options that are quarkus build time only can be with quarkus, but all the other Camel options should b

[GitHub] [camel-k] lburgazzoli opened a new pull request #803: Revert "chore: Re-enable e2e tests"

lburgazzoli opened a new pull request #803: Revert "chore: Re-enable e2e tests" URL: https://github.com/apache/camel-k/pull/803 Reverts apache/camel-k#802 This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-k] lburgazzoli opened a new issue #793: e2e tests are failing on travis

lburgazzoli opened a new issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [camel-k] lburgazzoli commented on issue #793: e2e tests are failing on travis

lburgazzoli commented on issue #793: e2e tests are failing on travis URL: https://github.com/apache/camel-k/issues/793#issuecomment-508377488 Failing again https://travis-ci.org/apache/camel-k/builds/554105978 This is an autom

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r299554684 ## File path: pkg/apis/camel/v1alpha1/integrationkit_types.go ## @@ -82,8 +82,10 @@ const ( // Inte

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r299554591 ## File path: pkg/apis/camel/v1alpha1/integration_types.go ## @@ -142,8 +142,10 @@ const ( // Integ

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r299553723 ## File path: pkg/apis/camel/v1alpha1/build_types.go ## @@ -64,8 +64,12 @@ const ( // BuildKind --

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r300269439 ## File path: pkg/controller/integration/integration_controller.go ## @@ -224,48 +226,62 @@ func (r *Reconc

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r300268704 ## File path: pkg/controller/build/build_controller.go ## @@ -161,37 +162,58 @@ func (r *ReconcileBuild) Re

[GitHub] [camel-k] astefanutti commented on a change in pull request #799: Move waiting for platform to controller

astefanutti commented on a change in pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#discussion_r300269852 ## File path: pkg/controller/integrationkit/integrationkit_controller.go ## @@ -141,42 +143,55 @@ func (r *

[GitHub] [camel-quarkus] ppalaga commented on issue #8: quarkus-camel - Migrate option prefixes

ppalaga commented on issue #8: quarkus-camel - Migrate option prefixes URL: https://github.com/apache/camel-quarkus/issues/8#issuecomment-508397815 Posted our standpoint on quarkus-dev: https://groups.google.com/d/msg/quarkus-dev/eyLaDlACNoE/mi7AQsC7CgAJ ---

[GitHub] [camel-k] jamesnetherton opened a new issue #804: Nil pointer on build failure recovery

jamesnetherton opened a new issue #804: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/issues/804 I wanted to simulate a build failure so I did: ``` $ kamel run --dependency=camel-foobar examples/hello.xml ``` Which made the operator crash:

[GitHub] [camel-k] jamesnetherton opened a new pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton opened a new pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805 fixes #804 This is an automated message from the Apache Git Service. To respond to the

[GitHub] [camel-k] lburgazzoli commented on issue #799: Move waiting for platform to controller

lburgazzoli commented on issue #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#issuecomment-508418940 @astefanutti findings should have been fixed, mind doing another review ? This

[GitHub] [camel-quarkus] ppalaga commented on issue #7: Upgrade to Camel SNAPSHOT

ppalaga commented on issue #7: Upgrade to Camel SNAPSHOT URL: https://github.com/apache/camel-quarkus/issues/7#issuecomment-508427365 The proposed `camel-snapshot` profile is fine as long as camel-quarkus does not need to get (backwards incompatibly) adapted to API changes in Camel. Such c

[GitHub] [camel-k] jamesnetherton opened a new issue #806: Updating an integration leaves it stuck in phase Deploying

jamesnetherton opened a new issue #806: Updating an integration leaves it stuck in phase Deploying URL: https://github.com/apache/camel-k/issues/806 Just tried the following: ``` $ kamel run examples/hello.xml integration "hello" created ``` Tweaked the `` value. Then:

[GitHub] [camel-k] lburgazzoli commented on issue #806: Updating an integration leaves it stuck in phase Deploying

lburgazzoli commented on issue #806: Updating an integration leaves it stuck in phase Deploying URL: https://github.com/apache/camel-k/issues/806#issuecomment-508446701 Yes this is a know issue, should be solved by a pr currently under review On Thu, 4 Jul 2019 at 13:03, James Nether

[GitHub] [camel-quarkus] ppalaga opened a new pull request #35: Fix #10 Produce test-jars of the integration tests

ppalaga opened a new pull request #35: Fix #10 Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/pull/35 This is what I hope would make it possible to run our integration tests inside the planned Quarkus Platform. @aloubyansky could you please review,

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300324114 ## File path: pkg/controller/build/recovery.go ## @@ -95,7 +95,9 @@ func (action *errorRecoveryAction) H

[GitHub] [camel-k] jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300377526 ## File path: pkg/controller/build/recovery.go ## @@ -95,7 +95,9 @@ func (action *errorRecoveryAction

[GitHub] [camel-quarkus] aloubyansky commented on issue #35: Fix #10 Produce test-jars of the integration tests

aloubyansky commented on issue #35: Fix #10 Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/pull/35#issuecomment-508466089 I will look into that. This is an automated message from the A

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300378611 ## File path: pkg/controller/build/recovery.go ## @@ -95,7 +95,9 @@ func (action *errorRecoveryAction) H

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300379226 ## File path: pkg/controller/build/recovery.go ## @@ -95,7 +95,9 @@ func (action *errorRecoveryAction) H

[GitHub] [camel-k] jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300379885 ## File path: pkg/controller/build/recovery.go ## @@ -95,7 +95,9 @@ func (action *errorRecoveryAction

[GitHub] [camel-k] astefanutti commented on issue #799: Move waiting for platform to controller

astefanutti commented on issue #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799#issuecomment-508469811 LGTM! This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-k] lburgazzoli merged pull request #803: Revert "chore: Re-enable e2e tests"

lburgazzoli merged pull request #803: Revert "chore: Re-enable e2e tests" URL: https://github.com/apache/camel-k/pull/803 This is an automated message from the Apache Git Service. To respond to the message, please log on to G

[GitHub] [camel-k] astefanutti merged pull request #799: Move waiting for platform to controller

astefanutti merged pull request #799: Move waiting for platform to controller URL: https://github.com/apache/camel-k/pull/799 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [camel-k] astefanutti closed issue #797: Move waiting for platform to controller

astefanutti closed issue #797: Move waiting for platform to controller URL: https://github.com/apache/camel-k/issues/797 This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

[GitHub] [camel-k] lburgazzoli closed issue #806: Updating an integration leaves it stuck in phase Deploying

lburgazzoli closed issue #806: Updating an integration leaves it stuck in phase Deploying URL: https://github.com/apache/camel-k/issues/806 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [camel-k] lburgazzoli commented on issue #806: Updating an integration leaves it stuck in phase Deploying

lburgazzoli commented on issue #806: Updating an integration leaves it stuck in phase Deploying URL: https://github.com/apache/camel-k/issues/806#issuecomment-508506314 Fixed as part of #799 799 This is an automated message

[GitHub] [camel-k] lburgazzoli edited a comment on issue #806: Updating an integration leaves it stuck in phase Deploying

lburgazzoli edited a comment on issue #806: Updating an integration leaves it stuck in phase Deploying URL: https://github.com/apache/camel-k/issues/806#issuecomment-508506314 Fixed as part of #799 This is an automated messa

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300429131 ## File path: pkg/controller/build/recovery.go ## @@ -87,8 +87,6 @@ func (action *errorRecoveryAction) H

[GitHub] [camel-quarkus] davsclaus commented on issue #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus

davsclaus commented on issue #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus URL: https://github.com/apache/camel-quarkus/pull/23#issuecomment-508510162 LGTM, lets merge it, thanks @ppalaga This

[GitHub] [camel-quarkus] davsclaus merged pull request #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus

davsclaus merged pull request #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus URL: https://github.com/apache/camel-quarkus/pull/23 This is an automated message from the Apache Git Service. To re

[GitHub] [camel-quarkus] davsclaus closed issue #6: Initial source code - Package names

davsclaus closed issue #6: Initial source code - Package names URL: https://github.com/apache/camel-quarkus/issues/6 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-quarkus] oscerd commented on issue #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus

oscerd commented on issue #23: Fix #6 Rename packages from io.quarkus.camel to org.apache.camel.quarkus URL: https://github.com/apache/camel-quarkus/pull/23#issuecomment-508510201 +1 This is an automated message from the Apac

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #36: Release first version of camel-quarkus

lburgazzoli opened a new issue #36: Release first version of camel-quarkus URL: https://github.com/apache/camel-quarkus/issues/36 Once #24 is fixed we should do a first version of camel-quarkus, drop camel bits from quarkus repo and get a new quarkus release that includes our camel bits -

[GitHub] [camel-k] jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300453032 ## File path: pkg/controller/build/recovery.go ## @@ -87,8 +87,6 @@ func (action *errorRecoveryAction

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300454205 ## File path: pkg/controller/build/recovery.go ## @@ -87,8 +87,6 @@ func (action *errorRecoveryAction) H

[GitHub] [camel-k] jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300454980 ## File path: pkg/controller/build/recovery.go ## @@ -87,8 +87,6 @@ func (action *errorRecoveryAction

[GitHub] [camel-website] Nayananga opened a new pull request #49: fixes for page not found errors

Nayananga opened a new pull request #49: fixes for page not found errors URL: https://github.com/apache/camel-website/pull/49 Sorry for not being active in this week, My new semester began since I could`t do much. Hopefully do better in this weekend

[GitHub] [camel-k] jamesnetherton opened a new issue #807: Dependencies & rest-dsl traits are never enabled

jamesnetherton opened a new issue #807: Dependencies & rest-dsl traits are never enabled URL: https://github.com/apache/camel-k/issues/807 Follow up investigation to my [observation](https://github.com/apache/camel-k/pull/805#discussion_r300453032) in #805. The cause of the problem

[GitHub] [camel-website] zregvart merged pull request #49: fixes for page not found errors

zregvart merged pull request #49: fixes for page not found errors URL: https://github.com/apache/camel-website/pull/49 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [camel-website] zregvart commented on issue #49: fixes for page not found errors

zregvart commented on issue #49: fixes for page not found errors URL: https://github.com/apache/camel-website/pull/49#issuecomment-508678348 Thank you :) This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-k] jamesnetherton opened a new pull request #808: fix: Dependencies & rest-dsl traits are never enabled

jamesnetherton opened a new pull request #808: fix: Dependencies & rest-dsl traits are never enabled URL: https://github.com/apache/camel-k/pull/808 fixes #807 This is an automated message from the Apache Git Service. To resp

[GitHub] [camel-k] lburgazzoli commented on issue #766: Add conditions to camel-k CRs

lburgazzoli commented on issue #766: Add conditions to camel-k CRs URL: https://github.com/apache/camel-k/pull/766#issuecomment-508717975 > Love it! > > Two general comments: > > * Currently, conditions are shared among CRs, so it is possible to mix them, I wonder whether ther

[GitHub] [camel-k] lburgazzoli closed issue #807: Dependencies & rest-dsl traits are never enabled

lburgazzoli closed issue #807: Dependencies & rest-dsl traits are never enabled URL: https://github.com/apache/camel-k/issues/807 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [camel-k] lburgazzoli merged pull request #808: fix: Dependencies & rest-dsl traits are never enabled

lburgazzoli merged pull request #808: fix: Dependencies & rest-dsl traits are never enabled URL: https://github.com/apache/camel-k/pull/808 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [camel-k] jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery

jamesnetherton commented on a change in pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805#discussion_r300831589 ## File path: pkg/controller/build/recovery.go ## @@ -87,8 +87,6 @@ func (action *errorRecoveryAction

[GitHub] [camel-k] lburgazzoli closed issue #804: Nil pointer on build failure recovery

lburgazzoli closed issue #804: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/issues/804 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [camel-k] lburgazzoli merged pull request #805: fix: Nil pointer on build failure recovery

lburgazzoli merged pull request #805: fix: Nil pointer on build failure recovery URL: https://github.com/apache/camel-k/pull/805 This is an automated message from the Apache Git Service. To respond to the message, please log

<    5   6   7   8   9   10   11   12   13   14   >