[GitHub] [camel-quarkus] oscerd closed issue #45: Use caffein as LRUCache in native mode

2019-07-08 Thread GitBox
oscerd closed issue #45: Use caffein as LRUCache in native mode URL: https://github.com/apache/camel-quarkus/issues/45 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [camel-quarkus] oscerd closed issue #44: Infinispan substrate test are disbaled

2019-07-08 Thread GitBox
oscerd closed issue #44: Infinispan substrate test are disbaled URL: https://github.com/apache/camel-quarkus/issues/44 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [camel-quarkus] oscerd merged pull request #46: Caffeine

2019-07-08 Thread GitBox
oscerd merged pull request #46: Caffeine URL: https://github.com/apache/camel-quarkus/pull/46 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

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Dmitry Volodin
+1 (binding) Thanks, Gregor! -- Best regards, Dmitry Volodin вс, 7 июл. 2019 г. в 12:17, Gregor Zurowski : > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the > fourth milestone towards a new 3.0.0 major release with another 105 > improvements and fixes. > > R

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Willem Jiang
+1 (binding) Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Jul 7, 2019 at 5:17 PM Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the > fourth milestone towards a new 3.0.0 major release with another 105 > improvements and f

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Freeman Fang
+1 (non-binding) Thanks! - Freeman(Yue) Fang Red Hat, Inc. > On Jul 7, 2019, at 5:16 AM, Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the > fourth milestone towards a new 3.0.0 major release with another 105 > impr

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Claus Ibsen
And you need to add camel-main as dependency (well the maven plugin may bring it itself but its good practice to have it too in the pom) On Mon, Jul 8, 2019 at 9:25 PM Claus Ibsen wrote: > > Hi > > Ah okay that is because you need to migrate as the shutdown strategy > class has moved to a new pac

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Claus Ibsen
Hi Ah okay that is because you need to migrate as the shutdown strategy class has moved to a new package You can also set the timeout in application.properties with camel.main.shutdown-timeout=5 Then you dont need the anymore On Mon, Jul 8, 2019 at 9:09 PM Federico Valeri wrote: > > Hi Cla

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Federico Valeri
Hi Claus, I did several tests for #1 and I can confirm the issue. You can also try yourself using this simple example: - https://github.com/fvaleri/fuse-examples/tree/master/stan/jdbc-transaction (2.24.1) - https://github.com/fvaleri/fuse-examples/tree/camel3m4/stan/jdbc-transaction (3.0.0-M4)

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Claus Ibsen
Hi Can you create a ticket for #2 For #1 sounds like the file is not in the target/classes folder, at the time you run the app. Can you double check. On Mon, Jul 8, 2019 at 7:36 PM Federico Valeri wrote: > > +1 > > A couple of minor issues I found while doing M4 tests on my support > projects: >

[GitHub] [camel-quarkus] lburgazzoli opened a new pull request #47: Use RestAssured in JDBC test

2019-07-08 Thread GitBox
lburgazzoli opened a new pull request #47: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/pull/47 Fixes #42 This is an automated message from the Apache Git Service. To respond to the message, please

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Federico Valeri
+1 A couple of minor issues I found while doing M4 tests on my support projects: 1. Usually, I run the command "mvn clean camel:run" to test Spring use cases, with the context definition in "META-INF/spring/camel.xml". This is working fine on 2.x, but I have the following Exception on 3.x ( note

[GitHub] [camel-quarkus] lburgazzoli merged pull request #43: chore: ignore ObjectStore folder

2019-07-08 Thread GitBox
lburgazzoli merged pull request #43: chore: ignore ObjectStore folder URL: https://github.com/apache/camel-quarkus/pull/43 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [camel-quarkus] lburgazzoli opened a new pull request #46: Caffeine

2019-07-08 Thread GitBox
lburgazzoli opened a new pull request #46: Caffeine URL: https://github.com/apache/camel-quarkus/pull/46 Fixes #44 Fixes #45 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [camel-quarkus] lburgazzoli commented on issue #45: Use caffein as LRUCache in native mode

2019-07-08 Thread GitBox
lburgazzoli commented on issue #45: Use caffein as LRUCache in native mode URL: https://github.com/apache/camel-quarkus/issues/45#issuecomment-509300938 As part of camel M3, the system property `CamelSimpleLRUCacheFactory` is not more effective and the choice of the LRU Cache to use depends

[GitHub] [camel-k-runtime] lburgazzoli merged pull request #92: improve kotlin support

2019-07-08 Thread GitBox
lburgazzoli merged pull request #92: improve kotlin support URL: https://github.com/apache/camel-k-runtime/pull/92 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

[GitHub] [camel-k-runtime] lburgazzoli merged pull request #91: improve groovy support

2019-07-08 Thread GitBox
lburgazzoli merged pull request #91: improve groovy support URL: https://github.com/apache/camel-k-runtime/pull/91 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #45: Use caffein as LRUCache in native mode

2019-07-08 Thread GitBox
lburgazzoli opened a new issue #45: Use caffein as LRUCache in native mode URL: https://github.com/apache/camel-quarkus/issues/45 In native mode, camel-core uses a `SimpleLRUCache` https://github.com/apache/camel-quarkus/blob/master/extensions/core/deployment/src/main/java/org/apache/camel/

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #44: Infinispan substrate test are disbaled

2019-07-08 Thread GitBox
lburgazzoli opened a new issue #44: Infinispan substrate test are disbaled URL: https://github.com/apache/camel-quarkus/issues/44 Investigate https://github.com/quarkusio/quarkus/issues/2351 This is an automated message from t

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #42: Use RestAssured in JDBC test

2019-07-08 Thread GitBox
lburgazzoli opened a new issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42 So we use the same style of other tests This is an automated message from the Apache Git Service. To respo

[GitHub] [camel-k-runtime] lburgazzoli opened a new pull request #92: improve kotlin support

2019-07-08 Thread GitBox
lburgazzoli opened a new pull request #92: improve kotlin support URL: https://github.com/apache/camel-k-runtime/pull/92 - add missing methods from route builder / builder support - add initial support for kotlin auto completion in idea ---

[GitHub] [camel-k-runtime] lburgazzoli commented on issue #83: Experimental IDE auto-completion using grape

2019-07-08 Thread GitBox
lburgazzoli commented on issue #83: Experimental IDE auto-completion using grape URL: https://github.com/apache/camel-k-runtime/pull/83#issuecomment-509240261 superseded by #91 91 This is an automated message from the Apache G

[GitHub] [camel-k-runtime] lburgazzoli closed pull request #83: Experimental IDE auto-completion using grape

2019-07-08 Thread GitBox
lburgazzoli closed pull request #83: Experimental IDE auto-completion using grape URL: https://github.com/apache/camel-k-runtime/pull/83 This is an automated message from the Apache Git Service. To respond to the message, pl

[GitHub] [camel-k-runtime] lburgazzoli opened a new pull request #91: improve groovy support

2019-07-08 Thread GitBox
lburgazzoli opened a new pull request #91: improve groovy support URL: https://github.com/apache/camel-k-runtime/pull/91 - add missing methods from route builder / builder support - initial support for idea auto completion

[GitHub] [camel-quarkus] ppalaga opened a new issue #41: Re-introduce test scope in integration test projects

2019-07-08 Thread GitBox
ppalaga opened a new issue #41: Re-introduce test scope in integration test projects URL: https://github.com/apache/camel-quarkus/issues/41 Once https://github.com/quarkusio/quarkus/issues/3136 get resolved, we can make our integration test projects idiomatic again. This would mean (at lea

[GitHub] [camel-quarkus] lburgazzoli merged pull request #35: Fix #10 Produce test-jars of the integration tests

2019-07-08 Thread GitBox
lburgazzoli merged pull request #35: Fix #10 Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/pull/35 This is an automated message from the Apache Git Service. To respond to the message

[GitHub] [camel-quarkus] lburgazzoli closed issue #10: Produce test-jars of the integration tests

2019-07-08 Thread GitBox
lburgazzoli closed issue #10: Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/issues/10 This is an automated message from the Apache Git Service. To respond to the message, please log o

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Zoran Regvart
+1 (binding) Thanks Gregor! zoran On Sun, Jul 7, 2019 at 11:17 AM Gregor Zurowski wrote: > > Hi Everyone: > > This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the > fourth milestone towards a new 3.0.0 major release with another 105 > improvements and fixes. > > Release notes: >

[GitHub] [camel-quarkus] oscerd merged pull request #40: Manage camel-servlet and camel-aws-sns in the BOM

2019-07-08 Thread GitBox
oscerd merged pull request #40: Manage camel-servlet and camel-aws-sns in the BOM URL: https://github.com/apache/camel-quarkus/pull/40 This is an automated message from the Apache Git Service. To respond to the message, plea

[GitHub] [camel-website] oscerd opened a new pull request #55: Fixed Table for Sha512

2019-07-08 Thread GitBox
oscerd opened a new pull request #55: Fixed Table for Sha512 URL: https://github.com/apache/camel-website/pull/55 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [camel-website] oscerd merged pull request #55: Fixed Table for Sha512

2019-07-08 Thread GitBox
oscerd merged pull request #55: Fixed Table for Sha512 URL: https://github.com/apache/camel-website/pull/55 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

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

2019-07-08 Thread GitBox
lburgazzoli edited a comment on issue #766: Add conditions to camel-k CRs URL: https://github.com/apache/camel-k/pull/766#issuecomment-509191235 @astefanutti @nicolaferraro we still miss to additional information such as the config maps that the integration creates/requires among the condit

[GitHub] [camel-website] oscerd merged pull request #54: Only SHA512 files should be used in releases tables

2019-07-08 Thread GitBox
oscerd merged pull request #54: Only SHA512 files should be used in releases tables URL: https://github.com/apache/camel-website/pull/54 This is an automated message from the Apache Git Service. To respond to the message, pl

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

2019-07-08 Thread GitBox
lburgazzoli edited a comment on issue #766: Add conditions to camel-k CRs URL: https://github.com/apache/camel-k/pull/766#issuecomment-509190925 So I've added a little bit more logic and now if you describe an integration while it is building a kit you'll see something like: ```yaml

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

2019-07-08 Thread GitBox
lburgazzoli commented on issue #766: Add conditions to camel-k CRs URL: https://github.com/apache/camel-k/pull/766#issuecomment-509191235 @astefanutti @nicolaferraro we still miss to include additional information in the conditions but didn't want to make the PR too big, can you please revi

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

2019-07-08 Thread GitBox
lburgazzoli commented on issue #766: Add conditions to camel-k CRs URL: https://github.com/apache/camel-k/pull/766#issuecomment-509190925 So I've added a little bit more logic and now if you describe an integration while it is building a kit you'll see something like: ``` Name:

[GitHub] [camel-quarkus] ppalaga commented on issue #40: Manage camel-servlet and camel-aws-sns in the BOM

2019-07-08 Thread GitBox
ppalaga commented on issue #40: Manage camel-servlet and camel-aws-sns in the BOM URL: https://github.com/apache/camel-quarkus/pull/40#issuecomment-509186886 TravisCI attached to my fork passed: https://travis-ci.org/ppalaga/camel-quarkus/builds/555720536 -

[GitHub] [camel-quarkus] ppalaga opened a new pull request #40: Manage camel-servlet and camel-aws-sns in the BOM

2019-07-08 Thread GitBox
ppalaga opened a new pull request #40: Manage camel-servlet and camel-aws-sns in the BOM URL: https://github.com/apache/camel-quarkus/pull/40 This becomes required when Camel stuff is removed from Quarkus BOM This is an autom

[GitHub] [camel-k] lburgazzoli commented on issue #600: Testing Camel K integrations

2019-07-08 Thread GitBox
lburgazzoli commented on issue #600: Testing Camel K integrations URL: https://github.com/apache/camel-k/issues/600#issuecomment-509173285 We could then report test results through [conditions](https://github.com/apache/camel-k/issues/594) -

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

2019-07-08 Thread GitBox
aloubyansky commented on issue #35: Fix #10 Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/pull/35#issuecomment-509171973 I think so. This is an automated message from the Apache Git S

[GitHub] [camel-k] nicolaferraro commented on issue #600: Testing Camel K integrations

2019-07-08 Thread GitBox
nicolaferraro commented on issue #600: Testing Camel K integrations URL: https://github.com/apache/camel-k/issues/600#issuecomment-509171773 After some brainstorming here and there I'd proceed with a POC about that. We want to remain without project structure for camel k integrations,

[GitHub] [camel-website] oscerd opened a new pull request #54: Only SHA512 files should be used in releases tables

2019-07-08 Thread GitBox
oscerd opened a new pull request #54: Only SHA512 files should be used in releases tables URL: https://github.com/apache/camel-website/pull/54 This is an automated message from the Apache Git Service. To respond to the messa

[GitHub] [camel-k] lburgazzoli closed issue #692: Add version information to all resources

2019-07-08 Thread GitBox
lburgazzoli closed issue #692: Add version information to all resources URL: https://github.com/apache/camel-k/issues/692 This is an automated message from the Apache Git Service. To respond to the message, please log on to G

[GitHub] [camel-k] lburgazzoli merged pull request #782: Initial upgrade support

2019-07-08 Thread GitBox
lburgazzoli merged pull request #782: Initial upgrade support URL: https://github.com/apache/camel-k/pull/782 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

[GitHub] [camel-website] oscerd merged pull request #53: 2.22.x train

2019-07-08 Thread GitBox
oscerd merged pull request #53: 2.22.x train URL: https://github.com/apache/camel-website/pull/53 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL ab

[GitHub] [camel-quarkus] oscerd commented on issue #36: Release first version of camel-quarkus

2019-07-08 Thread GitBox
oscerd commented on issue #36: Release first version of camel-quarkus URL: https://github.com/apache/camel-quarkus/issues/36#issuecomment-509156429 Also we need to apply the ASF release style to the POM, like we have in camel-k-runtime or camel. At least we need to double check all is alrea

[GitHub] [camel-website] oscerd opened a new pull request #53: 2.22.x train

2019-07-08 Thread GitBox
oscerd opened a new pull request #53: 2.22.x train URL: https://github.com/apache/camel-website/pull/53 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [camel-quarkus] ppalaga opened a new issue #39: Move Bean test out of Core integration test

2019-07-08 Thread GitBox
ppalaga opened a new issue #39: Move Bean test out of Core integration test URL: https://github.com/apache/camel-quarkus/issues/39 This is an automated message from the Apache Git Service. To respond to the message, please lo

[GitHub] [camel-quarkus] ppalaga commented on issue #36: Release first version of camel-quarkus

2019-07-08 Thread GitBox
ppalaga commented on issue #36: Release first version of camel-quarkus URL: https://github.com/apache/camel-quarkus/issues/36#issuecomment-509153469 Update: To release camel-quarkus 0.0.1 we need: * A Quarkus release (presumably 0.19.0) that contains the following fixes/changes:

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

2019-07-08 Thread GitBox
ppalaga commented on issue #35: Fix #10 Produce test-jars of the integration tests URL: https://github.com/apache/camel-quarkus/pull/35#issuecomment-509149186 Is this good to merge, @aloubyansky ? This is an automated message

[GitHub] [camel-website] oscerd merged pull request #52: Added release 2.22.0

2019-07-08 Thread GitBox
oscerd merged pull request #52: Added release 2.22.0 URL: https://github.com/apache/camel-website/pull/52 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-website] oscerd opened a new pull request #52: Added release 2.22.0

2019-07-08 Thread GitBox
oscerd opened a new pull request #52: Added release 2.22.0 URL: https://github.com/apache/camel-website/pull/52 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-website] oscerd merged pull request #51: Release 2.23.x train

2019-07-08 Thread GitBox
oscerd merged pull request #51: Release 2.23.x train URL: https://github.com/apache/camel-website/pull/51 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-website] oscerd opened a new pull request #51: Release 2.23.x train

2019-07-08 Thread GitBox
oscerd opened a new pull request #51: Release 2.23.x train URL: https://github.com/apache/camel-website/pull/51 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 opened a new issue #38: Website

2019-07-08 Thread GitBox
lburgazzoli opened a new issue #38: Website URL: https://github.com/apache/camel-quarkus/issues/38 - include camel-quarkus among camel's projects in the upcoming camel [webside](https://camel.apache.org/staging/) - create a website ---

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #37: Documentation

2019-07-08 Thread GitBox
lburgazzoli opened a new issue #37: Documentation URL: https://github.com/apache/camel-quarkus/issues/37 - migrate doc from quarkusio here - update quarkusio doc to point tofdoc here This is an automated message from the Ap

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Jean-Baptiste Onofré
+1 (binding) Regards JB Le 8 juil. 2019 à 09:49, à 09:49, Andrea Cosentino a écrit: >+1 (binding) > >Thanks Gregor! > >-- >Andrea Cosentino  >-- >Apache Camel PMC Chair >Apache Karaf Committer >Apache Servicemix PMC Member >Email: ancosen1...@yahoo.com >Twitter:

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Andrea Cosentino
+1 (binding) Thanks Gregor! -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Sunday, July 7, 2019, 11:17:23 AM GMT+2, Gregor Zurowski wrote:

Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-08 Thread Alex Dettinger
+1 (binding) Thanks Gregor, Alex On Sun, Jul 7, 2019 at 1:55 PM Claus Ibsen wrote: > +1 (binding) > > Tested with CiA2 source code. > > The migration from m3 to m4 commit is here > > https://github.com/camelinaction/camelinaction2/commit/655a8146f1b375c23ddca150cbb018d434121632 > > On Sun, Jul

[GitHub] [camel-website] zregvart commented on issue #50: fix for external link errors, and dropdown navbar-link menu items were set to unclickable

2019-07-08 Thread GitBox
zregvart commented on issue #50: fix for external link errors, and dropdown navbar-link menu items were set to unclickable URL: https://github.com/apache/camel-website/pull/50#issuecomment-509112721 Thanks! This is an automat

[GitHub] [camel-website] zregvart merged pull request #50: fix for external link errors, and dropdown navbar-link menu items were set to unclickable

2019-07-08 Thread GitBox
zregvart merged pull request #50: fix for external link errors, and dropdown navbar-link menu items were set to unclickable URL: https://github.com/apache/camel-website/pull/50 This is an automated message from the Apache Gi