[GitHub] [camel-quarkus] lburgazzoli commented on issue #4: Initial source code - Add license headers

2019-07-01 Thread GitBox
lburgazzoli commented on issue #4: Initial source code - Add license headers URL: https://github.com/apache/camel-quarkus/issues/4#issuecomment-507546243 @ppalaga I'm taking it as I'm working to something related This is an au

[GitHub] [camel-quarkus] davsclaus opened a new pull request #21: Use vanilla Maven Compiler Plugin version (from maven central)

2019-07-01 Thread GitBox
davsclaus opened a new pull request #21: Use vanilla Maven Compiler Plugin version (from maven central) URL: https://github.com/apache/camel-quarkus/pull/21 This is an automated message from the Apache Git Service. To respon

[GitHub] [camel-quarkus] davsclaus opened a new issue #20: Avoid 3rd party maven repositories if possible

2019-07-01 Thread GitBox
davsclaus opened a new issue #20: Avoid 3rd party maven repositories if possible URL: https://github.com/apache/camel-quarkus/issues/20 Noticed during build that something is downloaded from ``` [INFO] [INFO] --- formatter-maven-plugin:2.8.1:format (default) @ camel-quarkus-build-p

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #19: Configure license check

2019-07-01 Thread GitBox
lburgazzoli opened a new issue #19: Configure license check URL: https://github.com/apache/camel-quarkus/issues/19 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

[GitHub] [camel-quarkus] oscerd merged pull request #13: Add keys

2019-07-01 Thread GitBox
oscerd merged pull request #13: Add keys URL: https://github.com/apache/camel-quarkus/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [camel-quarkus] oscerd opened a new issue #18: Add Camel-AWS-EKS extension

2019-07-01 Thread GitBox
oscerd opened a new issue #18: Add Camel-AWS-EKS extension URL: https://github.com/apache/camel-quarkus/issues/18 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [camel-quarkus] oscerd opened a new issue #17: Add Camel-AWS-ECS extension

2019-07-01 Thread GitBox
oscerd opened a new issue #17: Add Camel-AWS-ECS extension URL: https://github.com/apache/camel-quarkus/issues/17 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [camel-quarkus] oscerd opened a new issue #16: Add Camel-AWS-KMS extension

2019-07-01 Thread GitBox
oscerd opened a new issue #16: Add Camel-AWS-KMS extension URL: https://github.com/apache/camel-quarkus/issues/16 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

Re: one more contributing user :)

2019-07-01 Thread Andrea Cosentino
Hello, We can add you to the list of contributors. To become committer the process is a bit more complex and longer. Thanks. Il giorno mar 2 lug 2019 alle ore 07:41 Otávio Prado < otaviofelipedopr...@gmail.com> ha scritto: > Hello everyone, everything good? I would like to have my name added on

[GitHub] [camel-k-runtime] lburgazzoli merged pull request #88: Enable checkstyle and license checks

2019-07-01 Thread GitBox
lburgazzoli merged pull request #88: Enable checkstyle and license checks URL: https://github.com/apache/camel-k-runtime/pull/88 This is an automated message from the Apache Git Service. To respond to the message, please log

one more contributing user :)

2019-07-01 Thread Otávio Prado
Hello everyone, everything good? I would like to have my name added on the list of camel apache commiters, it would be a great honor for me :) Name: Otávio Prado Thank you guys!

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #14: Configure checkstyle

2019-07-01 Thread GitBox
lburgazzoli opened a new issue #14: Configure checkstyle URL: https://github.com/apache/camel-quarkus/issues/14 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 commented on issue #784: Refactor controller logic

2019-07-01 Thread GitBox
lburgazzoli commented on issue #784: Refactor controller logic URL: https://github.com/apache/camel-k/pull/784#issuecomment-507512999 @astefanutti ready for review This is an automated message from the Apache Git Service. To r

[GitHub] [camel-k] lburgazzoli closed pull request #775: chore(ci): try to speedup travis build

2019-07-01 Thread GitBox
lburgazzoli closed pull request #775: chore(ci): try to speedup travis build URL: https://github.com/apache/camel-k/pull/775 This is an automated message from the Apache Git Service. To respond to the message, please log on t

[GitHub] [camel-k] lburgazzoli commented on issue #775: chore(ci): try to speedup travis build

2019-07-01 Thread GitBox
lburgazzoli commented on issue #775: chore(ci): try to speedup travis build URL: https://github.com/apache/camel-k/pull/775#issuecomment-507512712 manually merged This is an automated message from the Apache Git Service. To re

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI

2019-07-01 Thread GitBox
lburgazzoli commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/pull/12#discussion_r299245902 ## File path: .travis.yml ## @@ -1,9 +1,19 @@ language: java jdk: - openjdk8 +env: + global: +

[GitHub] [camel-quarkus] ppalaga commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI

2019-07-01 Thread GitBox
ppalaga commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/pull/12#discussion_r299242616 ## File path: .travis.yml ## @@ -1,9 +1,19 @@ language: java jdk: - openjdk8 +env: + global: +-

[GitHub] [camel-quarkus] ppalaga commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI

2019-07-01 Thread GitBox
ppalaga commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/pull/12#discussion_r299242616 ## File path: .travis.yml ## @@ -1,9 +1,19 @@ language: java jdk: - openjdk8 +env: + global: +-

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI

2019-07-01 Thread GitBox
lburgazzoli commented on a change in pull request #12: Fix #11 Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/pull/12#discussion_r299213491 ## File path: .travis.yml ## @@ -1,9 +1,19 @@ language: java jdk: - openjdk8 +env: + global: +

[GitHub] [camel-quarkus] lburgazzoli closed issue #5: Initial source code - Maven GAV

2019-07-01 Thread GitBox
lburgazzoli closed issue #5: Initial source code - Maven GAV URL: https://github.com/apache/camel-quarkus/issues/5 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

[GitHub] [camel-k] nicolaferraro opened a new issue #789: Wrong example on operator hub

2019-07-01 Thread GitBox
nicolaferraro opened a new issue #789: Wrong example on operator hub URL: https://github.com/apache/camel-k/issues/789 The integration doesn't run any route, because we expect multiple sources, not a single one: https://github.com/apache/camel-k/blob/fbd3d7fcbd7992ecb19d20211b6f1c2ad7d43d8

[GitHub] [camel-k] nicolaferraro merged pull request #787: chore(travis): disable e2e

2019-07-01 Thread GitBox
nicolaferraro merged pull request #787: chore(travis): disable e2e URL: https://github.com/apache/camel-k/pull/787 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

[GitHub] [camel-quarkus] ppalaga opened a new pull request #12: Fix #11 Test the native mode on TravisCI

2019-07-01 Thread GitBox
ppalaga opened a new pull request #12: Fix #11 Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [camel-k] lburgazzoli opened a new pull request #788: chore(travis): verbose integration tests

2019-07-01 Thread GitBox
lburgazzoli opened a new pull request #788: chore(travis): verbose integration tests URL: https://github.com/apache/camel-k/pull/788 This is only to test e2e test failures This is an automated message from the Apache Git Serv

[GitHub] [camel-quarkus] ppalaga opened a new issue #11: Test the native mode on TravisCI

2019-07-01 Thread GitBox
ppalaga opened a new issue #11: Test the native mode on TravisCI URL: https://github.com/apache/camel-quarkus/issues/11 This is an automated message from the Apache Git Service. To respond to the message, please log on to Git

[GitHub] [camel-quarkus] lburgazzoli merged pull request #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
lburgazzoli merged pull request #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3 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 #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
ppalaga commented on issue #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3#issuecomment-507359291 4e0ac7b is based on Quarkus tag 0.18.0 This is an automated message from the Apach

[GitHub] [camel-k] lburgazzoli merged pull request #783: Route trait does not work if route.auto is set to false

2019-07-01 Thread GitBox
lburgazzoli merged pull request #783: Route trait does not work if route.auto is set to false URL: https://github.com/apache/camel-k/pull/783 This is an automated message from the Apache Git Service. To respond to the messag

[GitHub] [camel-k] lburgazzoli closed issue #767: Route trait does not work if route.auto is set to false

2019-07-01 Thread GitBox
lburgazzoli closed issue #767: Route trait does not work if route.auto is set to false URL: https://github.com/apache/camel-k/issues/767 This is an automated message from the Apache Git Service. To respond to the message, pl

Re: Build startup speed

2019-07-01 Thread Claus Ibsen
Hi +1 I think this is good and would be great to get the speedup. And yes camel-bom should be the BOM that end users will use and import And camel-parent should be for the internal usage of the Camel project itself. On Mon, Jul 1, 2019 at 3:40 PM Guillaume Nodet wrote: > > Ah, good point. T

[GitHub] [camel-k] lburgazzoli commented on issue #783: Route trait does not work if route.auto is set to false

2019-07-01 Thread GitBox
lburgazzoli commented on issue #783: Route trait does not work if route.auto is set to false URL: https://github.com/apache/camel-k/pull/783#issuecomment-507292999 @nicolaferraro ok, changed the impl and removed `auto` for the trait as it does not make sense --

Re: Build startup speed

2019-07-01 Thread Guillaume Nodet
Ah, good point. This was definitely not expected. It seems to be a side effect of the generation of the BOM by the bom-generator-maven-plugin which uses the dependency management section of the parent I suppose. This would definitely need to be reworked if there's a consensus to go ahead in this

Re: Build startup speed

2019-07-01 Thread Willem Jiang
Hi Guillaume, I checked the PR[1], the dependencies of camel components in the bom/camel-bom/pom.xml were removed. Please double check it if I missed anything. [1]https://github.com/apache/camel/pull/3009 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jul 1, 2019 at 8:31 PM Guillaum

Re: Build startup speed

2019-07-01 Thread Guillaume Nodet
'm not talking about modifying the camel-bom, but the camel-parent. So this should mostly affect project that inherit from camel-parent, and I don't think that's the correct way of using camel, users should import the bom instead, since CAMEL-8502. Le lun. 1 juil. 2019 à 14:25, Willem Jiang a éc

Re: Build startup speed

2019-07-01 Thread Willem Jiang
When user use the bom file, they don't need to specify the version of camel-xxx component. If we remove the dependency management section form BOM, the old pom.xml may not work any more. They need to specify the camel version for the camel-xxx component in their pom. We need to inform the end use

[GitHub] [camel-k] lburgazzoli merged pull request #786: chore: extract indentedwriter to it's own package and make it an utility

2019-07-01 Thread GitBox
lburgazzoli merged pull request #786: chore: extract indentedwriter to it's own package and make it an utility URL: https://github.com/apache/camel-k/pull/786 This is an automated message from the Apache Git Service. To resp

Re: Build startup speed

2019-07-01 Thread Andrea Cosentino
In my opinion, this makes completely sense. Il giorno lun 1 lug 2019 alle ore 14:10 Guillaume Nodet ha scritto: > I've been spending quite some time last week to try to improve the time > spent by maven before actually starting building something. > I've opened a few PR on maven which should red

Build startup speed

2019-07-01 Thread Guillaume Nodet
I've been spending quite some time last week to try to improve the time spent by maven before actually starting building something. I've opened a few PR on maven which should reduce by 50% the time, but I noticed that a lot of time is spent because the camel parent pom has 800 dependencies in the d

[GitHub] [camel-quarkus] oscerd commented on issue #6: Initial source code - Package names

2019-07-01 Thread GitBox
oscerd commented on issue #6: Initial source code - Package names URL: https://github.com/apache/camel-quarkus/issues/6#issuecomment-507235866 I think we cannot leave the package with the old name. We can import with that package name, merge and then change the package name completely with

[GitHub] [camel-quarkus] ppalaga opened a new issue #10: Produce test-jars of the extensions

2019-07-01 Thread GitBox
ppalaga opened a new issue #10: Produce test-jars of the extensions URL: https://github.com/apache/camel-quarkus/issues/10 This is to allow the (planned) Quarkus platform repo to run our tests. This is an automated message fro

[GitHub] [camel-quarkus] davsclaus commented on issue #4: Initial source code - Add license headers

2019-07-01 Thread GitBox
davsclaus commented on issue #4: Initial source code - Add license headers URL: https://github.com/apache/camel-quarkus/issues/4#issuecomment-507218904 Yes after the initial port we should migrate it to have ASF license headers and packaging name and so on. We cannot accept source co

[GitHub] [camel-quarkus] ppalaga commented on issue #4: Initial source code - Add license headers

2019-07-01 Thread GitBox
ppalaga commented on issue #4: Initial source code - Add license headers URL: https://github.com/apache/camel-quarkus/issues/4#issuecomment-507218261 You mean the headers should be changed also in files coming from the Quarkus repo? I have `Thou shall not change license/copyright/authors he

[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
lburgazzoli edited a comment on issue #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3#issuecomment-507213448 camel- is used for all the component, starter and so on, that's what I meant so perhaps extensions should follow the same naming convent

[GitHub] [camel-quarkus] ppalaga commented on issue #6: Initial source code - Package names

2019-07-01 Thread GitBox
ppalaga commented on issue #6: Initial source code - Package names URL: https://github.com/apache/camel-quarkus/issues/6#issuecomment-507215729 I wonder whether the java package renaming should be a part of the code migration from the Quarkus repo? I could try to modify my import scr

[GitHub] [camel-quarkus] ppalaga commented on issue #5: Initial source code - Maven GAV

2019-07-01 Thread GitBox
ppalaga commented on issue #5: Initial source code - Maven GAV URL: https://github.com/apache/camel-quarkus/issues/5#issuecomment-507213586 This is done in the last commit of #3 , currently 8ecbd58. I think the current issue can be closed. --

[GitHub] [camel-quarkus] lburgazzoli commented on issue #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
lburgazzoli commented on issue #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3#issuecomment-507213448 camel- is used for all the component, starter and so on, that's what I meant T

[GitHub] [camel-quarkus] ppalaga commented on issue #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
ppalaga commented on issue #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3#issuecomment-507212610 > > ``` > > `camel-` removed from some directory names > > ``` > > > Not having a strong opinion here but since the other camel pro

Re: Quarkus

2019-07-01 Thread Willem Jiang
Hi Peter, Thanks for the clarification, in this case you don't need to do any paperwork. Happy hacking camel quarkus code :) Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jul 1, 2019 at 5:54 PM Peter Palaga wrote: > > Hi Willem, > > I signed the ICLA on 2012-02-20 when I was activ

[GitHub] [camel-k] astefanutti merged pull request #785: refactor(trait): replace resources and execute post action as part of trait management

2019-07-01 Thread GitBox
astefanutti merged pull request #785: refactor(trait): replace resources and execute post action as part of trait management URL: https://github.com/apache/camel-k/pull/785 This is an automated message from the Apache Git Se

Re: Quarkus

2019-07-01 Thread Peter Palaga
Hi Willem, I signed the ICLA on 2012-02-20 when I was active in another ASF project. So I hope there is nothing else I should do now? Thanks, -- Peter On 01/07/2019 03:57, Willem Jiang wrote: Hi, I just went through the code commit logs of quarkus camel extension, lots of commits are from

[GitHub] [camel-quarkus] ppalaga commented on issue #3: Migrate Camel extensions from Quarkus

2019-07-01 Thread GitBox
ppalaga commented on issue #3: Migrate Camel extensions from Quarkus URL: https://github.com/apache/camel-quarkus/pull/3#issuecomment-507191878 > @ppalaga can we do 1 thing at time ? i.e. the travis thing can be a seprate PR that can be merged independently from the migration one Of