[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301776149 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301776149 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301776149 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301776149 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
lburgazzoli commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301776149 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] ppalaga commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
ppalaga commented on a change in pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55#discussion_r301746791 ## File path: integration-tests/infinispan/pom.xml ## @@ -0,0 +1,154 @@ + +

[GitHub] [camel-quarkus] ppalaga opened a new pull request #55: Fix #31 Move infinispan integration-tests out of core

2019-07-09 Thread GitBox
ppalaga opened a new pull request #55: Fix #31 Move infinispan integration-tests out of core URL: https://github.com/apache/camel-quarkus/pull/55 This is an automated message from the Apache Git Service. To respond to the

Re: Issue using the noop=true with idempotent=true

2019-07-09 Thread Deepak Anand
Thanks Claus for you response. The same files can be present in different sub directory , so I need checksum to identify them. How in the file endpoint I can generate the checksum and add it to the idempotentRepository . May be a silly question but I am new to Camel earlier I was generating the

Re: Issue using the noop=true with idempotent=true

2019-07-09 Thread Claus Ibsen
Set idempotentRepository on the file endpoint instead and remove idempotent consumer in the route. On Tue, Jul 9, 2019 at 7:01 PM Deepak Anand wrote: > > Hi Devs , > > I have a requirement to read from a directory where there are no of files > in the subdirectories of it . I am using the camel

Issue using the noop=true with idempotent=true

2019-07-09 Thread Deepak Anand
Hi Devs , I have a requirement to read from a directory where there are no of files in the subdirectories of it . I am using the camel File component for it . I don't want to process the same file which has been processed earlier using an idempotentConsumer and using RedisCache for it. In the

[GitHub] [camel-quarkus] alainpham opened a new issue #54: camel application property routesUri is not overridden at runtime

2019-07-09 Thread GitBox
alainpham opened a new issue #54: camel application property routesUri is not overridden at runtime URL: https://github.com/apache/camel-quarkus/issues/54 **Describe the bug** When using the camel extension, the application property `quarkus.camel.routes-uris` is not overridden at run

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

2019-07-09 Thread GitBox
lburgazzoli closed issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

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

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

[GitHub] [camel-quarkus] ppalaga commented on issue #52: Removed Jenkinsfile not used

2019-07-09 Thread GitBox
ppalaga commented on issue #52: Removed Jenkinsfile not used URL: https://github.com/apache/camel-quarkus/pull/52#issuecomment-509637711 Yes, I can see a bit more when I log in, but https://builds.apache.org/job/camel-quarkus-pr/configure/ still returns 404. But actually, there is a

[GitHub] [camel-quarkus] oscerd commented on issue #52: Removed Jenkinsfile not used

2019-07-09 Thread GitBox
oscerd commented on issue #52: Removed Jenkinsfile not used URL: https://github.com/apache/camel-quarkus/pull/52#issuecomment-509628864 You should already have read access to the ui with your ASF account. To modify the stuff you need to be committer.

[GitHub] [camel-quarkus] ppalaga commented on issue #52: Removed Jenkinsfile not used

2019-07-09 Thread GitBox
ppalaga commented on issue #52: Removed Jenkinsfile not used URL: https://github.com/apache/camel-quarkus/pull/52#issuecomment-509628082 So the PR job on ASF Jenkins is now configured via Jenkins UI, right? What can I do to get read access to those settings?

[GitHub] [camel-quarkus] lburgazzoli merged pull request #53: chore(build): remove travis build

2019-07-09 Thread GitBox
lburgazzoli merged pull request #53: chore(build): remove travis build URL: https://github.com/apache/camel-quarkus/pull/53 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [camel-quarkus] lburgazzoli merged pull request #52: Removed Jenkinsfile not used

2019-07-09 Thread GitBox
lburgazzoli merged pull request #52: Removed Jenkinsfile not used URL: https://github.com/apache/camel-quarkus/pull/52 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [camel-quarkus] oscerd opened a new pull request #52: Removed Jenkinsfile not used

2019-07-09 Thread GitBox
oscerd opened a new pull request #52: Removed Jenkinsfile not used URL: https://github.com/apache/camel-quarkus/pull/52 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [camel-quarkus] oscerd closed pull request #51: Test PR on Jenkins do not merge

2019-07-09 Thread GitBox
oscerd closed pull request #51: Test PR on Jenkins do not merge URL: https://github.com/apache/camel-quarkus/pull/51 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [camel-quarkus] lburgazzoli commented on issue #51: Test PR on Jenkins do not merge

2019-07-09 Thread GitBox
lburgazzoli commented on issue #51: Test PR on Jenkins do not merge URL: https://github.com/apache/camel-quarkus/pull/51#issuecomment-509618261 Looks much better, it also got https://github.com/apache/camel-quarkus/pull/47 run successfully so I'd go for disable travis for the moment

[GitHub] [camel-quarkus] oscerd commented on issue #49: chore(build): add Jenkinsfile

2019-07-09 Thread GitBox
oscerd commented on issue #49: chore(build): add Jenkinsfile URL: https://github.com/apache/camel-quarkus/pull/49#issuecomment-509595442 This was just an attempt. With the standard ASF infra approach we may need to use a personal access token of a personal account to be able to scan the

[GitHub] [camel-quarkus] ppalaga commented on issue #49: chore(build): add Jenkinsfile

2019-07-09 Thread GitBox
ppalaga commented on issue #49: chore(build): add Jenkinsfile URL: https://github.com/apache/camel-quarkus/pull/49#issuecomment-509594898 The motivation for this is because we have hit the memory limits of TravisCI in https://github.com/apache/camel-quarkus/pull/47 , right? Anybody

[GitHub] [camel-quarkus] oscerd opened a new pull request #51: Test PR on Jenkins do not merge

2019-07-09 Thread GitBox
oscerd opened a new pull request #51: Test PR on Jenkins do not merge URL: https://github.com/apache/camel-quarkus/pull/51 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[HEADS UP] - javax.activation API moved out of camel-core

2019-07-09 Thread Claus Ibsen
Hi Just a heads up about https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13678 The javax.activation API was used in camel-core for the Attachments support on the Message API. The javax.activation API was built in JDK8 and removed from JDK9+ onwards. So users on Java 11 had "difficult"

[GitHub] [camel-quarkus] oscerd merged pull request #50: Do not use io.quarkus...FeatureBuildItem feature constants

2019-07-09 Thread GitBox
oscerd merged pull request #50: Do not use io.quarkus...FeatureBuildItem feature constants URL: https://github.com/apache/camel-quarkus/pull/50 This is an automated message from the Apache Git Service. To respond to the

[GitHub] [camel-quarkus] ppalaga opened a new pull request #50: Do not use io.quarkus...FeatureBuildItem feature constants

2019-07-09 Thread GitBox
ppalaga opened a new pull request #50: Do not use io.quarkus...FeatureBuildItem feature constants URL: https://github.com/apache/camel-quarkus/pull/50 Those constants will be removed from Quarkus together with Camel extensions

[GitHub] [camel-quarkus] lburgazzoli commented on issue #42: Use RestAssured in JDBC test

2019-07-09 Thread GitBox
lburgazzoli commented on issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42#issuecomment-509581815 You can add one if you wish This is an automated message from the Apache Git

[GitHub] [camel-quarkus] ppalaga commented on issue #42: Use RestAssured in JDBC test

2019-07-09 Thread GitBox
ppalaga commented on issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42#issuecomment-509580310 > No one is saying that we should ban tests that do not use resteasy Nice to hear that. My standpoint is that we should have one or more itests

[GitHub] [camel-quarkus] oscerd merged pull request #48: chore(arc): add ConsumerTemplate and ProducerTemplate producers

2019-07-09 Thread GitBox
oscerd merged pull request #48: chore(arc): add ConsumerTemplate and ProducerTemplate producers URL: https://github.com/apache/camel-quarkus/pull/48 This is an automated message from the Apache Git Service. To respond to

[GitHub] [camel-quarkus] lburgazzoli commented on issue #42: Use RestAssured in JDBC test

2019-07-09 Thread GitBox
lburgazzoli commented on issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42#issuecomment-509574993 > I see at least two reasons why we might not want to do this: > > 1. Practical: adding resteasy bloats the native image a bit.

[GitHub] [camel-quarkus] oscerd merged pull request #49: chore(build): add Jenkinsfile

2019-07-09 Thread GitBox
oscerd merged pull request #49: chore(build): add Jenkinsfile URL: https://github.com/apache/camel-quarkus/pull/49 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [camel-quarkus] ppalaga commented on issue #42: Use RestAssured in JDBC test

2019-07-09 Thread GitBox
ppalaga commented on issue #42: Use RestAssured in JDBC test URL: https://github.com/apache/camel-quarkus/issues/42#issuecomment-509569867 I see at least two reasons why we might not want to do this: 1. Practical: adding resteasy bloats the native image a bit. Compilation will take

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

2019-07-09 Thread Claus Ibsen
On Tue, Jul 9, 2019 at 9:02 AM Federico Valeri wrote: > > Yes I use the new pkg for DefaultShutdownStrategy in camel3m4 branch of the > example and I think already have camel-main dep: > > [*INFO*] +- org.apache.camel:camel-spring:jar:3.0.0-M4:compile > > [*INFO*] | +-

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

2019-07-09 Thread Francois Papon
+1 (non-binding) Thanks for the release! regards, François fpa...@apache.org Le 07/07/2019 à 11:16, Gregor Zurowski a écrit : > 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 >

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

2019-07-09 Thread Federico Valeri
Yes I use the new pkg for DefaultShutdownStrategy in camel3m4 branch of the example and I think already have camel-main dep: [*INFO*] +- org.apache.camel:camel-spring:jar:3.0.0-M4:compile [*INFO*] | +- org.apache.camel:camel-main:jar:3.0.0-M4:compile [*INFO*] | | \-

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

2019-07-09 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

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

2019-07-09 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

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

2019-07-09 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-09 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. > >