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 @@
+
+
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 @@
+
+
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 @@
+
+
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 @@
+
+
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 @@
+
+
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 @@
+
+
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
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
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
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
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
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
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
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
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.
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?
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
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
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
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
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
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
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
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
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"
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
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
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
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
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
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.
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
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
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*] | +-
+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
>
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*] | | \-
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
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
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
+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.
>
>
40 matches
Mail list logo