+1
---
Luca Burgazzoli
On Thu, Jul 25, 2019 at 1:55 PM Andrea Cosentino
wrote:
> Here the correct staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1144/
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf
On Fri, Jul 26, 2019 at 5:22 AM Willem Jiang wrote:
>
> +1 for the upgrading the component name.
> Here are my quick question about the documentation. There may be some
> changes between Camel 3 and Camel 2.
> How can we warning the user the name is changed?
>
In the migration guide where we hav
+1 for the upgrading the component name.
Here are my quick question about the documentation. There may be some
changes between Camel 3 and Camel 2.
How can we warning the user the name is changed?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Jul 25, 2019 at 6:34 PM Claus Ibsen wr
Nayananga opened a new pull request #62: microdata added about twitter account
and few more additional details
URL: https://github.com/apache/camel-website/pull/62
I added a twitter account link and a little description about the camel from
google search. please let me know if there any co
+1
On Thu, Jul 25, 2019 at 7:14 PM Claus Ibsen wrote:
> I logged a ticket to rename the other components, then we have a clean
> start for Camel 3
> https://issues.apache.org/jira/browse/CAMEL-13792
>
> On Thu, Jul 25, 2019 at 12:33 PM Claus Ibsen
> wrote:
> >
> > On Thu, Jul 25, 2019 at 12:24
Hello all:
This is a combined vote to release Apache Camel K 1.0.0-M1 and Apache Camel
K Runtime 1.0.0.
Apache Camel K Runtime versions follow a different convention (without
milestones) and won't necessarily match main Camel K versions in the future.
Runtime staging repository:
https://reposito
zregvart merged pull request #61: antora footer edited
URL: https://github.com/apache/camel-website/pull/61
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
Nayananga opened a new pull request #61: antora footer edited
URL: https://github.com/apache/camel-website/pull/61
I added camel hugo footer into antora camel theme footer
This is an automated message from the Apache Git Servi
Le jeu. 25 juil. 2019 à 20:28, Zoran Regvart a écrit :
> Hi Guillaume,
> since we're all piling up on you :) One more thing I'd like you to
> consider :)
>
> I find Velocity templates a bit brittle and hard to maintain, would
> you consider a Java code generator to create the Java source code?
>
+1
Regards
JB
Le 25 juil. 2019 à 20:31, à 20:31, Zoran Regvart a écrit:
>+1 I'm so delighted that we'll consider/are doing this :) I do think
>that Camel as a framework should take on the responsibility to hide
>these details from the user, user wants to invoke HTTP endpoints, the
>user doesn't
+1
Thanks!
－
Freeman(Yue) Fang
Red Hat, Inc.
> On Jul 25, 2019, at 5:48 AM, Claus Ibsen wrote:
>
> Hi
>
> So what has been bothering Camel 2.x users is that when they use http
> they would likely use the camel-http4 component and then they should
> use http4 as the component
Hi
Model driven makes sense.
I like velocity but I understand Zoran's comment.
Maybe we can imagine some pluggable: pojo describing model and binding.
Regards
JB
Le 25 juil. 2019 à 20:28, à 20:28, Zoran Regvart a écrit:
>Hi Guillaume,
>since we're all piling up on you :) One more thing I'd li
+1 I'm so delighted that we'll consider/are doing this :) I do think
that Camel as a framework should take on the responsibility to hide
these details from the user, user wants to invoke HTTP endpoints, the
user doesn't care which version of HTTP Components/Netty/Jetty... is
under the hood.
zoran
Hi Guillaume,
since we're all piling up on you :) One more thing I'd like you to consider :)
I find Velocity templates a bit brittle and hard to maintain, would
you consider a Java code generator to create the Java source code?
I've found JavaPoet[1] pretty nifty in this regard. I've used it for
Nayananga opened a new pull request #60: added microdata to antora footer.hbs
URL: https://github.com/apache/camel-website/pull/60
This is an automated message from the Apache Git Service.
To respond to the message, please l
zregvart merged pull request #60: added microdata to antora footer.hbs
URL: https://github.com/apache/camel-website/pull/60
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
asf-ci commented on issue #95: Omit the artifactId in release tags
URL: https://github.com/apache/camel-quarkus/pull/95#issuecomment-515062507
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/49/
---
lburgazzoli merged pull request #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77
This is an automated message from the Apache Git Service.
To respond to the message, please log
ppalaga commented on issue #96: Make CamelRuntime smart to decide deferInitPhase
URL: https://github.com/apache/camel-quarkus/issues/96#issuecomment-515052957
@gnodet noted in a call that this is not going to get resolved with Camel
3.0.0. We agreed to keep using the manual `deferInitPhase`
ppalaga opened a new issue #96: Make CamelRuntime smart to decide deferInitPhase
URL: https://github.com/apache/camel-quarkus/issues/96
Currently, `deferInitPhase` true or false needs to be decided by the
application developer depending on whether she wants to pass different config
values
asf-ci commented on issue #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#issuecomment-515039994
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/48/
oscerd merged pull request #879: Fix make clean for tests and remove binary
file from repo
URL: https://github.com/apache/camel-k/pull/879
This is an automated message from the Apache Git Service.
To respond to the message,
oscerd merged pull request #94: Fix typo s/AWs_REGION/AWS_REGION/
URL: https://github.com/apache/camel-quarkus/pull/94
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
oscerd commented on issue #94: Fix typo s/AWs_REGION/AWS_REGION/
URL: https://github.com/apache/camel-quarkus/pull/94#issuecomment-515028672
Thanks
This is an automated message from the Apache Git Service.
To respond to the me
lburgazzoli commented on issue #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#issuecomment-515028570
@ppalaga 0.20.0 is expected to be released in 5 days (week-end included) and
after that release the snapshot profile won't be active by defa
ppalaga opened a new pull request #95: Omit the artifactId in release tags
URL: https://github.com/apache/camel-quarkus/pull/95
This is an automated message from the Apache Git Service.
To respond to the message, please log o
ppalaga commented on issue #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#issuecomment-515025458
> added snapshot profile active by default for the moment as there were some
changes in quarkus like moving to GraalVM 19.1.1 that have introduc
lburgazzoli commented on a change in pull request #77: Move test packages to
org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#discussion_r307270283
##
File path:
integration-tests/aws/src/main/java/org/apache/camel/quarkus/component/aws/CamelRoute.java
###
dmvolod opened a new pull request #879: Fix make clean for tests and remove
binary file from repo
URL: https://github.com/apache/camel-k/pull/879
@nicolaferraro , i will wounder, if testing binary file in repo requires for
some reasons
-
ppalaga commented on a change in pull request #77: Move test packages to
org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#discussion_r307269097
##
File path:
integration-tests/aws/src/main/java/org/apache/camel/quarkus/component/aws/CamelRoute.java
##
lburgazzoli commented on a change in pull request #77: Move test packages to
org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#discussion_r307265972
##
File path:
integration-tests/aws/src/main/java/org/apache/camel/quarkus/component/aws/CamelRoute.java
###
asf-ci commented on issue #94: Fix typo s/AWs_REGION/AWS_REGION/
URL: https://github.com/apache/camel-quarkus/pull/94#issuecomment-515020645
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/47/
-
Couple of questions:
- how does this play with external components ?
- what about annotations we have now i.e. for endpoints ? I found
particularity useful that types, enum values and so one are taken from the
java code
---
Luca Burgazzoli
On Thu, Jul 25, 2019 at 12:04 PM Claus Ibsen wrote:
>
+1
---
Luca Burgazzoli
On Thu, Jul 25, 2019 at 1:58 PM Francois Papon
wrote:
> Agree, it make sense!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 25/07/2019 à 12:23, Tadayoshi Sato a écrit :
> > +1
> >
> > Maybe it's also good time to review other components that have similar
> > varia
ppalaga commented on a change in pull request #77: Move test packages to
org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#discussion_r307258925
##
File path:
integration-tests/aws/src/main/java/org/apache/camel/quarkus/component/aws/CamelRoute.java
##
Agree, it make sense!
regards,
François
fpa...@apache.org
Le 25/07/2019 à 12:23, Tadayoshi Sato a écrit :
> +1
>
> Maybe it's also good time to review other components that have similar
> variants.
>
> On Thu, Jul 25, 2019 at 7:09 PM Alex Dettinger
> wrote:
>
>> +1
>>
>> On Thu, Jul 25, 2019 at
dmvolod commented on issue #863: operator-sdk build fails on latest master with
'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-515014867
https://github.com/operator-framework/operator-sdk/issues/1738
Here the correct staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1144/
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: osc
Hello all:
This is a vote to release Apache Camel Quarkus 0.0.2
This is the first release of the camel-quarkus project which contains the first
extensions for running Camel on Quarkus.
Staging repository:
Index of /repositories/orgapachecamel-1144
Tag:
https://gitbox.apache.org/repos/asf?p=cam
ipolyzos closed issue #869: make images fail on resolve of camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869
This is an automated message from the Apache Git Service.
To respond to the message, please log
ipolyzos commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-515006116
I can confirm that this issue is not present in a fresh copy.
Please see the log below:
>
> ---> e17c53f10082
ppalaga opened a new pull request #94: Fix typo s/AWs_REGION/AWS_REGION/
URL: https://github.com/apache/camel-quarkus/pull/94
This is an automated message from the Apache Git Service.
To respond to the message, please log on
I logged a ticket to rename the other components, then we have a clean
start for Camel 3
https://issues.apache.org/jira/browse/CAMEL-13792
On Thu, Jul 25, 2019 at 12:33 PM Claus Ibsen wrote:
>
> On Thu, Jul 25, 2019 at 12:24 PM Tadayoshi Sato
> wrote:
> >
> > +1
> >
> > Maybe it's also good time
nicolaferraro opened a new issue #878: Release Camel K 1.0.0 M1 and related
Camel K Runtime
URL: https://github.com/apache/camel-k/issues/878
Release notes:
- tbd
This is an automated message from the Apache Git Service.
T
asf-ci commented on issue #93: Added failIfNoTest option in surefire
configuration
URL: https://github.com/apache/camel-quarkus/pull/93#issuecomment-514997528
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/46/
ipolyzos edited a comment on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514993933
$ operator-sdk version
ipolyzos commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514993933
$ operator-sdk version
Hi
I am starting to work on this and will send a PR
On Wed, Jul 24, 2019 at 1:44 PM Claus Ibsen wrote:
>
> Hi
>
> JIRA ticket:
> https://issues.apache.org/jira/browse/CAMEL-13788
>
>
> So on the Camel Message API we have from Camel 1.0 an IN and OUT
> message that was based on the JBI and SOAP-W
On Thu, Jul 25, 2019 at 12:24 PM Tadayoshi Sato
wrote:
>
> +1
>
> Maybe it's also good time to review other components that have similar
> variants.
>
Yeah we have
- camel-quartz2
- camel-netty4
- camel-netty4-http
- camel-mongodb3
- camel-mina2
- camel-hdfs2
- camel-rxjava2
- camel-sjms2
> O
elasticsearch in Camel 3 exixts only as elasticsearch-rest scheme.
Il giorno gio 25 lug 2019 alle ore 12:31 Dmitry Volodin
ha scritto:
> +1
>
> And +1 to good idea from Tadayoshi as we have a set of the versions based
> components, like elastcisearch, jetty, quartz, etc.
> --
> Best regards,
> D
+1
And +1 to good idea from Tadayoshi as we have a set of the versions based
components, like elastcisearch, jetty, quartz, etc.
--
Best regards,
Dmitry Volodin
чт, 25 июл. 2019 г. в 13:24, Tadayoshi Sato :
> +1
>
> Maybe it's also good time to review other components that have similar
> varian
dmvolod commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514989322
Also please pull latest commits from upstream as some changes related to
build process were made
-
+1
Maybe it's also good time to review other components that have similar
variants.
On Thu, Jul 25, 2019 at 7:09 PM Alex Dettinger
wrote:
> +1
>
> On Thu, Jul 25, 2019 at 12:02 PM Andrea Cosentino
> wrote:
>
> > +1
> >
> > Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen <
> > claus.ib...@
asf-ci commented on issue #92: chore(build): move release profile to
camel-quarkus-parent
URL: https://github.com/apache/camel-quarkus/pull/92#issuecomment-514989062
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus
dmvolod commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514988905
@ipolyzos what is your operator-sdk version?
This is an automated m
+1
On Thu, Jul 25, 2019 at 12:02 PM Andrea Cosentino wrote:
> +1
>
> Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen <
> claus.ib...@gmail.com>
> ha scritto:
>
> > Hi
> >
> > So what has been bothering Camel 2.x users is that when they use http
> > they would likely use the camel-http4 comp
Hi
Btw a follow up question.
Would we be able to get to a point where all the model classes
(xxxDefinition and helpers etc) can be dropped at runtime, eg for
camel-quarkus optimization?
And also the refiers as they are the builder from model -> processor.
Well what you experiment with is surely
+1
Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen
ha scritto:
> Hi
>
> So what has been bothering Camel 2.x users is that when they use http
> they would likely use the camel-http4 component and then they should
> use http4 as the component name. The old camel-http component is
> deprecate
On Thu, Jul 25, 2019 at 11:28 AM Guillaume Nodet wrote:
>
> Le jeu. 25 juil. 2019 à 10:47, Claus Ibsen a écrit :
>
> > Hi
> >
> > Good to see more experiments, but as others have said in this mail
> > thread, its too overwhelming to dive into and understand.
> >
>
> Yes, I definitely get that, es
ipolyzos edited a comment on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514979902
A new issue later on the compilation of _pkg/trait/knative.go_ stops from
completing the images-dev build please see the log
ipolyzos commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514979902
A new issue later on the compilation of _pkg/trait/knative.go_ stops from
completing the images-dev build please see the log below
ipolyzos opened a new issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869
``` $ make images``` fails on the latest master due to unable to resolve
maven artifact.
Please see the error message below for more
> [IN
dmvolod commented on issue #863: operator-sdk build fails on latest master with
'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-514979096
@aldettinger, I'm fine with build right now.
Please pull latest master from upstream.
--
aldettinger commented on issue #863: operator-sdk build fails on latest master
with 'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-514979509
It may be another issue then, I'll investigate that. Many thanks @dmvolod .
---
Your point is really interesting.
However, I think one of the main problem right now is that the metamodel
information is spread in the whole source tree (some bits in camel-core,
and lots in the various components). This leads to a lot of hacks and
round trips in the build system (copying json f
+1
It's always difficult to tell people why they have to use http4 during
demos ;)
Nicola
On Thu, Jul 25, 2019 at 11:48 AM Claus Ibsen wrote:
> Hi
>
> So what has been bothering Camel 2.x users is that when they use http
> they would likely use the camel-http4 component and then they should
>
+1 Sounds good !
Le jeu. 25 juil. 2019 à 11:48, Claus Ibsen a écrit :
> Hi
>
> So what has been bothering Camel 2.x users is that when they use http
> they would likely use the camel-http4 component and then they should
> use http4 as the component name. The old camel-http component is
> depreca
Hi
So what has been bothering Camel 2.x users is that when they use http
they would likely use the camel-http4 component and then they should
use http4 as the component name. The old camel-http component is
deprecated as the http client it uses is EOL for many many years.
So with Camel 3 on the w
ipolyzos opened a new issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869
``` $ make images``` fails on the latest master due to unable to resolve
maven artifact.
Please see the error message below for more
> [IN
ipolyzos closed issue #869: make images fail on resolve of camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869
This is an automated message from the Apache Git Service.
To respond to the message, please log
ipolyzos commented on issue #869: make images fail on resolve of
camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869#issuecomment-514976641
@dmvolod, indeed building the [camel-k runtime
](https://github.com/apache/camel-k-runtime)solves this issue.
Thank you
--
ipolyzos closed issue #869: make images fail on resolve of camel-k-maven-plugin
URL: https://github.com/apache/camel-k/issues/869
This is an automated message from the Apache Git Service.
To respond to the message, please log
oscerd opened a new pull request #93: Added failIfNoTest option in surefire
configuration
URL: https://github.com/apache/camel-quarkus/pull/93
This is an automated message from the Apache Git Service.
To respond to the messa
oscerd merged pull request #93: Added failIfNoTest option in surefire
configuration
URL: https://github.com/apache/camel-quarkus/pull/93
This is an automated message from the Apache Git Service.
To respond to the message, pl
aldettinger commented on issue #863: operator-sdk build fails on latest master
with 'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-514974801
make images-dev still produce the same error in my environment with
operator-sdk v0.9.0, GO111MODULE=on and git up-
Le jeu. 25 juil. 2019 à 10:47, Claus Ibsen a écrit :
> Hi
>
> Good to see more experiments, but as others have said in this mail
> thread, its too overwhelming to dive into and understand.
>
Yes, I definitely get that, especially as it's still work in progress.
On the java dsl side, the goal is
oscerd merged pull request #92: chore(build): move release profile to
camel-quarkus-parent
URL: https://github.com/apache/camel-quarkus/pull/92
This is an automated message from the Apache Git Service.
To respond to the mess
Hi Guillaume & Cameleers,
I like that there's an effort to make the code more maintainable. I do
however feel that the source of truth is best kept in the Java code,
and perhaps this new model can be generated from that. I understand
the need for having a single strictly typed source of truth.
Cou
astefanutti commented on issue #863: operator-sdk build fails on latest master
with 'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-514960396
@dmvolod thanks a lot for your valuable inputs on this. Let us know the
outcome of the discussion upstream.
--
astefanutti closed issue #863: operator-sdk build fails on latest master with
'make images-dev'
URL: https://github.com/apache/camel-k/issues/863
This is an automated message from the Apache Git Service.
To respond to the me
astefanutti commented on issue #863: operator-sdk build fails on latest master
with 'make images-dev'
URL: https://github.com/apache/camel-k/issues/863#issuecomment-514959948
Let me close this as it should be fixed with #872. Feel free to re-open if
that is not the case.
-
nicolaferraro merged pull request #877: chore(js): fix examples, use arrow
function for lambda style processor
URL: https://github.com/apache/camel-k/pull/877
This is an automated message from the Apache Git Service.
To resp
nicolaferraro merged pull request #872: Remove Dep files
URL: https://github.com/apache/camel-k/pull/872
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
lburgazzoli merged pull request #871: chore(build): remove go mod vendor from
travis build
URL: https://github.com/apache/camel-k/pull/871
This is an automated message from the Apache Git Service.
To respond to the message,
Hi
Good to see more experiments, but as others have said in this mail
thread, its too overwhelming to dive into and understand.
So what I can see is that the model is now more "coded" in velocity vm
and xml xslt files, than what we had before with the java model
classes with JAXB annotations.
Als
lburgazzoli commented on issue #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#issuecomment-514956354
@ppalaga added snapshot profile active by default for the moment as there
were some changes in quarkus like moving to GraalVM 19.1.1 that ha
nicolaferraro closed issue #832: GC trait fails on some installations
URL: https://github.com/apache/camel-k/issues/832
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
nicolaferraro merged pull request #876: fix(GC): Skip 503 errors when scanning
for resources to be GCed
URL: https://github.com/apache/camel-k/pull/876
This is an automated message from the Apache Git Service.
To respond to
lburgazzoli merged pull request #116: Lambda processor doesn't work with JS
routes
URL: https://github.com/apache/camel-k-runtime/pull/116
This is an automated message from the Apache Git Service.
To respond to the message,
lburgazzoli closed issue #115: Lambda processor doesn't work with JS routes
URL: https://github.com/apache/camel-k-runtime/issues/115
This is an automated message from the Apache Git Service.
To respond to the message, please
zregvart merged pull request #58: added microdata to hugo footer.html
URL: https://github.com/apache/camel-website/pull/58
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
lburgazzoli commented on issue #874: chore(js): remove processor for js
examples because of a bug in graaljs
URL: https://github.com/apache/camel-k/pull/874#issuecomment-514950847
Will be fixed by https://github.com/apache/camel-k-runtime/pull/116
--
lburgazzoli closed pull request #874: chore(js): remove processor for js
examples because of a bug in graaljs
URL: https://github.com/apache/camel-k/pull/874
This is an automated message from the Apache Git Service.
To respo
lburgazzoli opened a new pull request #116: Lambda processor doesn't work with
JS routes
URL: https://github.com/apache/camel-k-runtime/pull/116
Fixes #115
This is an automated message from the Apache Git Service.
To respond
astefanutti opened a new pull request #876: fix(GC): Skip 503 errors when
scanning for resources to be GCed
URL: https://github.com/apache/camel-k/pull/876
Speculatively fixes #832.
This is an automated message from the Apach
Hi,
yes some examples to describe these new features would be great.
There are tones of changes which is a bit hard to follow at this stage (at
least for me)
On Wed, Jul 24, 2019 at 4:17 PM Andrea Cosentino wrote:
> Yeah, a concrete example of what has been done could be useful to better
> und
asf-ci commented on issue #77: Move test packages to org.apache.camel
URL: https://github.com/apache/camel-quarkus/pull/77#issuecomment-514930884
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/44/
lburgazzoli commented on issue #115: Lambda processor doesn't work with JS
routes
URL: https://github.com/apache/camel-k-runtime/issues/115#issuecomment-514929709
relates to https://github.com/oracle/graal/issues/1247
This is
lburgazzoli closed issue #873: Lambda processor doesn't work with JS routes
URL: https://github.com/apache/camel-k/issues/873
This is an automated message from the Apache Git Service.
To respond to the message, please log on
tadayosi opened a new issue #115: Lambda processor doesn't work with JS routes
URL: https://github.com/apache/camel-k-runtime/issues/115
Copied from apache/camel-k#873
With Camel K Client 1.0.0-M1-SNAPSHOT, `examples/routes.js` doesn't work as
follows:
```
$ kamel run --dev exa
1 - 100 of 102 matches
Mail list logo
