lburgazzoli commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-518975393
can’t we just fix the camel quarkus bom ?
about examples we could create a quickstart repo or put example so in
quarkus one,
Hello all:
This is a vote to release Apache Camel Quarkus 0.1.0
This is the second release of the camel-quarkus project which contains new
extensions and it has been updated to Camel Milestone 4.
Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1147/
Tag:
h
ppalaga commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519011164
> can’t we just fix the camel quarkus bom ?
Yeah, it could work (although encouraging users to inherit from a BOM may
sound stran
ppalaga opened a new issue #113: Document the release process
URL: https://github.com/apache/camel-quarkus/issues/113
@oscerd could you please create `RELEASING.adoc` or similar and document the
release process there? I'd need to know that not break the process when
working on https://git
WillemJiang opened a new issue #902: Road Map about Yaml DSL
URL: https://github.com/apache/camel-k/issues/902
I noticed that camel-k support yaml DSL recently. Is there any road map of
it?
Currently we are try to build DSL from the json definition, it looks like
using the yaml DSL dire
lburgazzoli commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519016616
> > can’t we just fix the camel quarkus bom ?
>
> Yeah, it could work (although encouraging users to inherit from a BOM may
s
lburgazzoli commented on issue #902: Road Map about Yaml DSL
URL: https://github.com/apache/camel-k/issues/902#issuecomment-519017594
The goal is to move it to apache camel once it becomes and stable enough and
feature complete so yes you’ll have LTS :)
lburgazzoli commented on issue #901: fix(examples): Remove references to
obsolete runtime argument
URL: https://github.com/apache/camel-k/pull/901#issuecomment-519019592
maybe this helps: https://restic.net/blog/2018-09-02/travis-build-cache
astefanutti commented on issue #901: fix(examples): Remove references to
obsolete runtime argument
URL: https://github.com/apache/camel-k/pull/901#issuecomment-519019971
Yes, +1 to try caching go modules.
This is an automated
jamesnetherton commented on issue #901: fix(examples): Remove references to
obsolete runtime argument
URL: https://github.com/apache/camel-k/pull/901#issuecomment-519022771
Ok - let me try adding some cache config as a separate PR.
--
ppalaga commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519023900
> > The main concern is to maintain the setup for end users separately from
ours (for building camel extensions) so that we accidentally
jamesnetherton opened a new pull request #903: fix(build): Cache go modules
directory
URL: https://github.com/apache/camel-k/pull/903
This is an automated message from the Apache Git Service.
To respond to the message, pleas
Hi Cameleers,
I brought up the issue of naming the JUnit 5 component without the
version and with 'jupiter' instead. The reason I brought this up is
because I think that we should shield the users from version changes
as much as possible. A version neutral name would allow us to move to
a future JU
Hi Community developers :)
on behalf of the Apache Camel project I would like to request that
Apache Camel stickers are made available at the ApacheCon NA and EU at
the ASF booths.
We have stickers available at the RedBubble store:
https://www.redbubble.com/people/comdev/works/32232604-apache-cam
lburgazzoli commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519032728
The test and related set-up we have as today are very simple and yes they
looks like examples but as long term I would expect to tes
ppalaga commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519037452
Yes, that sounds reasonable. How about having two categories of itests? One
usable as examples (perhaps in a separate directory called `
lburgazzoli commented on issue #112: Add a parent pom for end user applications
URL: https://github.com/apache/camel-quarkus/issues/112#issuecomment-519038912
we jus need examples, I would also build examples once a day or we are
likely to break your build time acceptance criteria :)
WillemJiang commented on issue #902: Road Map about Yaml DSL
URL: https://github.com/apache/camel-k/issues/902#issuecomment-519043286
Yeah, it's a good news.
This is an automated message from the Apache Git Service.
To respon
jamesnetherton merged pull request #903: fix(build): Cache go modules directory
URL: https://github.com/apache/camel-k/pull/903
This is an automated message from the Apache Git Service.
To respond to the message, please log o
+1 (binding)
---
Luca Burgazzoli
On Wed, Aug 7, 2019 at 9:39 AM Andrea Cosentino
wrote:
> Hello all:
>
> This is a vote to release Apache Camel Quarkus 0.1.0
>
> This is the second release of the camel-quarkus project which contains new
> extensions and it has been updated to Camel Milestone 4
astefanutti merged pull request #901: fix(examples): Remove references to
obsolete runtime argument
URL: https://github.com/apache/camel-k/pull/901
This is an automated message from the Apache Git Service.
To respond to the
Hey Zoran,
Thanks for bringing the version neutral name topic to this discussion.
As far as I can tell, the next major release of junit could even introduce
a new api with yet another name than jupiter.
But, then a good name could be camel-junit alone.
At this stage I would support camel-test
rejimathews commented on issue #902: Road Map about Yaml DSL
URL: https://github.com/apache/camel-k/issues/902#issuecomment-519131124
thats great! having a yaml dsl to code camel integrations. !
This is an automated message fr
It looks like we cannot replace camel-test module right now.
+1 with camel-test-junit5.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Aug 7, 2019 at 10:29 PM Alex Dettinger wrote:
>
> Hey Zoran,
>
> Thanks for bringing the version neutral name topic to this discussion.
> As far as
lburgazzoli opened a new issue #114: Move create-extension-templates to i.e.
tooling
URL: https://github.com/apache/camel-quarkus/issues/114
@ppalaga would it be possible to move create-extension-templates from
`extensions` to a top level directory like `tooling` ?
-
25 matches
Mail list logo
