> I assumed that we would release a Camel version and, perhaps shortly
> after, the Camel Spring Boot starters. I assumed that the Camel Spring
> Boot starters would have the same version as the Camel release.
I agree, the version parity between Camel and Camel Spring Boot (which
is implicitly ass
Hi Cameleers,
On Fri, Dec 20, 2019 at 9:33 AM Gregor Zurowski
wrote:
> I wanted to follow up on Andrea's question regarding the release
> process. As Guillaume already pointed out, one of the benefits of
> splitting Spring Boot support into a separate repository is to be able
> to support multip
Hi Everyone:
I wanted to follow up on Andrea's question regarding the release
process. As Guillaume already pointed out, one of the benefits of
splitting Spring Boot support into a separate repository is to be able
to support multiple Spring Boot versions. This would mean that the
Spring Boot su
Hi
For the docs/website, then I think camel-spring-boot should be similar
to camel-quarkus, where Spring Boot would be listed under "projects"
on the website.
And for camel-quarkus we have a tool that generates the list of
components, and its documentation.
https://github.com/apache/camel-quarkus
Hi
The -P fastinstall does not yet work, it still runs unit tests.
On Thu, Dec 12, 2019 at 4:27 PM Guillaume Nodet wrote:
>
> Things have progressed nicely:
> * the branch https://github.com/gnodet/camel/tree/CAMEL-14226 is the
> spring boot support
> * the branch https://github.com/gnodet/c
Hi Guillaume,
On Thu, Dec 12, 2019 at 4:27 PM Guillaume Nodet wrote:
> On the web site side of things, I haven't paid a close attention to how the
> web site is published. The camel source tree has some content (
> https://github.com/apache/camel/tree/master/docs), but how is that pushed
> to th
Things have progressed nicely:
* the branch https://github.com/gnodet/camel/tree/CAMEL-14226 is the
spring boot support
* the branch https://github.com/gnodet/camel/tree/CAMEL-14226-core is the
camel repo where spring-boot is deleted
All components relying on spring-boot (the camel-spring-boot
Le mar. 10 déc. 2019 à 10:35, Claus Ibsen a écrit :
> On Tue, Dec 10, 2019 at 10:19 AM Zoran Regvart wrote:
> >
> > Hi Guillaume,
> > +1 for the effort, I very much appreciate any effort to
> > simplify/speedup the build and separate the concerns.
> >
> > I would also like to know how the workfl
On Tue, Dec 10, 2019 at 10:19 AM Zoran Regvart wrote:
>
> Hi Guillaume,
> +1 for the effort, I very much appreciate any effort to
> simplify/speedup the build and separate the concerns.
>
> I would also like to know how the workflow for keeping the starters in
> sync would look like, would this be
The steps to perform when adding / removing a new camel component are still
to be defined.
Currently, what is working is the update of existing starters.
I think creating two goals to add / remove a starter can be easily done, so
that i could be done in an easy step. I'll work on that.
I've also s
Hi Guillaume,
+1 for the effort, I very much appreciate any effort to
simplify/speedup the build and separate the concerns.
I would also like to know how the workflow for keeping the starters in
sync would look like, would this be done by individually: on changes
to the Camel repository there need
Really good work!
I think this is just the first step, we can use a similar approach for the
others flavours.
But we need to document everything really well and we need to rethink about the
release process, I guess.
Thanks!
--
Andrea Cosentino
--
Apache Camel
Hi
+1
This is great stuff.
So just think how would the developer do when eg you add a new
component in the main Camel repo, lets call it components/camel-foobar
?
Then you go to camel-spring-boot and want to generate a
camel-foobar-starter because it should support SB too (Mind that not
all comp
13 matches
Mail list logo
