You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2019/07/04 04:48:16 UTC
Apache Camel 3 milestone 4 close down and release soon
Hi
I think we should close down on the last bits and get milestone 4
released and in the hands to the community.
We had a number of significant improvements and features such as:
1) Endpoint DSL
Type safe fluent builder for configuring endpoints in Java
2) Camel Main
Standalone Camel for microservices
Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
3) camel-core-engine
Tiny set of dependencies (only include absolutely what you need)
Needed by Camel K and Camel Quarkus to have smaller set of JARs on classpath
4) components depend on camel-support
Further reduced the dependency directly on camel-core for all set of
components. To ensure we use camel-api/camel-support for components
only.
5) lazy start producer
You can configure in the endpoint that the producer should lazy start
(eg on 1st message) you can use this to allow Camel to startup even if
the producer would fail on startup - but now that failure is deferred
to 1st message which you can then use Camels route error handler to
deal with etc
6) SPI for Reactive Engine
So we can plugin a different engine such as Camel Quarkus can benefit
from using its reactive engine.
7) DSL more extensive
The reifiers and DSL model is more extensive/expandable. For example a
new yaml dsl flow is developed at Camel K that required some of these
changes.
8) Properties component / placeholder
We can now easier extend this and also plugin to more 3rd parties such
as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
9) Usual stuff
Like bug fixes and whatnot.
I am currently working on getting the property component and
placeholder refactored so it works better and can easier to integrated
with other configuration libraries. Also it would allow us to
differentiate between read-only placeholders that can be loaded at
once, and others that are on-demand (eg to lookup in a database,
hashicorp vault etc.)
Also the CI build server is now 100% passing for the last couple of days.
So lets see if we can get the last bits done by end of tomorrow or end
of next week, and get a RC cut.
And we also need a M4 for both Camel K and Camel Quarkus to upgrade and use.
Any thoughts?
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Alex Dettinger <al...@gmail.com>.
+1
Alex
On Thu, Jul 4, 2019 at 7:43 AM Andrea Cosentino <an...@gmail.com> wrote:
> +1
>
> Il gio 4 lug 2019, 06:48 Claus Ibsen <cl...@gmail.com> ha scritto:
>
> > Hi
> >
> > I think we should close down on the last bits and get milestone 4
> > released and in the hands to the community.
> >
> > We had a number of significant improvements and features such as:
> >
> > 1) Endpoint DSL
> > Type safe fluent builder for configuring endpoints in Java
> >
> > 2) Camel Main
> > Standalone Camel for microservices
> > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> >
> > 3) camel-core-engine
> > Tiny set of dependencies (only include absolutely what you need)
> > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > classpath
> >
> > 4) components depend on camel-support
> > Further reduced the dependency directly on camel-core for all set of
> > components. To ensure we use camel-api/camel-support for components
> > only.
> >
> > 5) lazy start producer
> > You can configure in the endpoint that the producer should lazy start
> > (eg on 1st message) you can use this to allow Camel to startup even if
> > the producer would fail on startup - but now that failure is deferred
> > to 1st message which you can then use Camels route error handler to
> > deal with etc
> >
> > 6) SPI for Reactive Engine
> > So we can plugin a different engine such as Camel Quarkus can benefit
> > from using its reactive engine.
> >
> > 7) DSL more extensive
> > The reifiers and DSL model is more extensive/expandable. For example a
> > new yaml dsl flow is developed at Camel K that required some of these
> > changes.
> >
> > 8) Properties component / placeholder
> > We can now easier extend this and also plugin to more 3rd parties such
> > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> >
> > 9) Usual stuff
> > Like bug fixes and whatnot.
> >
> >
> > I am currently working on getting the property component and
> > placeholder refactored so it works better and can easier to integrated
> > with other configuration libraries. Also it would allow us to
> > differentiate between read-only placeholders that can be loaded at
> > once, and others that are on-demand (eg to lookup in a database,
> > hashicorp vault etc.)
> >
> > Also the CI build server is now 100% passing for the last couple of days.
> >
> > So lets see if we can get the last bits done by end of tomorrow or end
> > of next week, and get a RC cut.
> >
> > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> > use.
> >
> > Any thoughts?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
+1
Il gio 4 lug 2019, 06:48 Claus Ibsen <cl...@gmail.com> ha scritto:
> Hi
>
> I think we should close down on the last bits and get milestone 4
> released and in the hands to the community.
>
> We had a number of significant improvements and features such as:
>
> 1) Endpoint DSL
> Type safe fluent builder for configuring endpoints in Java
>
> 2) Camel Main
> Standalone Camel for microservices
> Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>
> 3) camel-core-engine
> Tiny set of dependencies (only include absolutely what you need)
> Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> classpath
>
> 4) components depend on camel-support
> Further reduced the dependency directly on camel-core for all set of
> components. To ensure we use camel-api/camel-support for components
> only.
>
> 5) lazy start producer
> You can configure in the endpoint that the producer should lazy start
> (eg on 1st message) you can use this to allow Camel to startup even if
> the producer would fail on startup - but now that failure is deferred
> to 1st message which you can then use Camels route error handler to
> deal with etc
>
> 6) SPI for Reactive Engine
> So we can plugin a different engine such as Camel Quarkus can benefit
> from using its reactive engine.
>
> 7) DSL more extensive
> The reifiers and DSL model is more extensive/expandable. For example a
> new yaml dsl flow is developed at Camel K that required some of these
> changes.
>
> 8) Properties component / placeholder
> We can now easier extend this and also plugin to more 3rd parties such
> as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>
> 9) Usual stuff
> Like bug fixes and whatnot.
>
>
> I am currently working on getting the property component and
> placeholder refactored so it works better and can easier to integrated
> with other configuration libraries. Also it would allow us to
> differentiate between read-only placeholders that can be loaded at
> once, and others that are on-demand (eg to lookup in a database,
> hashicorp vault etc.)
>
> Also the CI build server is now 100% passing for the last couple of days.
>
> So lets see if we can get the last bits done by end of tomorrow or end
> of next week, and get a RC cut.
>
> And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> use.
>
> Any thoughts?
>
>
>
>
>
>
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
Sounds good.
Il giorno ven 5 lug 2019 alle ore 14:35 Claus Ibsen <cl...@gmail.com>
ha scritto:
> And when its committed you can set the line length back to 250
>
> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > Thanks I got a word-wrap in the source code generate, will commit it
> > when it has regen the components
> >
> > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
> wrote:
> > >
> > > Fixed.
> > >
> > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
> ancosen@gmail.com>
> > > ha scritto:
> > >
> > > > We can override the property
> > > >
> > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > > >
> > > > We can put 10000
> > > >
> > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
> claus.ibsen@gmail.com>
> > > > ha scritto:
> > > >
> > > >> Hi
> > > >>
> > > >> Just a heads up that the checkstyle for endpoint-dsl will report
> some
> > > >> errors
> > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > > >>
> > > >> As this is generated we cannot keep the source files below 5000
> lines etc.
> > > >> And also some javadoc lines are long, as we would need to word-wrap
> > > >> them ourselves
> > > >> to make this shorter.
> > > >>
> > > >> But I assume the RC can be cut anyway, just skip CS for this module
> or in
> > > >> total.
> > > >>
> > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com>
> > > >> wrote:
> > > >> >
> > > >> > I've done with that documentation stuff. Gregor, when you are
> available,
> > > >> > let us know.
> > > >> >
> > > >> > Thanks
> > > >> >
> > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> > > >> ancosen@gmail.com>
> > > >> > ha scritto:
> > > >> >
> > > >> > > I should finish a couple of things on the AWS components for
> > > >> documenting
> > > >> > > the region stuff. I should finish soon and send email
> > > >> > >
> > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > > >> claus.ibsen@gmail.com>
> > > >> > > ha scritto:
> > > >> > >
> > > >> > >> Hi
> > > >> > >>
> > > >> > >> I think the master branch is ready for a RC cut.
> > > >> > >>
> > > >> > >> Let us know if/when you get started Gregor
> > > >> > >>
> > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > > >> gregor@list.zurowski.org>
> > > >> > >> wrote:
> > > >> > >> >
> > > >> > >> > +1
> > > >> > >> >
> > > >> > >> > I'll be available for cutting the RC.
> > > >> > >> >
> > > >> > >> > Thanks,
> > > >> > >> > Gregor
> > > >> > >> >
> > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
> claus.ibsen@gmail.com>
> > > >> > >> wrote:
> > > >> > >> > >
> > > >> > >> > > Hi
> > > >> > >> > >
> > > >> > >> > > I think we should close down on the last bits and get
> milestone 4
> > > >> > >> > > released and in the hands to the community.
> > > >> > >> > >
> > > >> > >> > > We had a number of significant improvements and features
> such as:
> > > >> > >> > >
> > > >> > >> > > 1) Endpoint DSL
> > > >> > >> > > Type safe fluent builder for configuring endpoints in Java
> > > >> > >> > >
> > > >> > >> > > 2) Camel Main
> > > >> > >> > > Standalone Camel for microservices
> > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
> bootstrap
> > > >> Camel
> > > >> > >> > >
> > > >> > >> > > 3) camel-core-engine
> > > >> > >> > > Tiny set of dependencies (only include absolutely what you
> need)
> > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of
> JARs
> > > >> on
> > > >> > >> classpath
> > > >> > >> > >
> > > >> > >> > > 4) components depend on camel-support
> > > >> > >> > > Further reduced the dependency directly on camel-core for
> all
> > > >> set of
> > > >> > >> > > components. To ensure we use camel-api/camel-support for
> > > >> components
> > > >> > >> > > only.
> > > >> > >> > >
> > > >> > >> > > 5) lazy start producer
> > > >> > >> > > You can configure in the endpoint that the producer should
> lazy
> > > >> start
> > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
> startup
> > > >> even if
> > > >> > >> > > the producer would fail on startup - but now that failure
> is
> > > >> deferred
> > > >> > >> > > to 1st message which you can then use Camels route error
> handler
> > > >> to
> > > >> > >> > > deal with etc
> > > >> > >> > >
> > > >> > >> > > 6) SPI for Reactive Engine
> > > >> > >> > > So we can plugin a different engine such as Camel Quarkus
> can
> > > >> benefit
> > > >> > >> > > from using its reactive engine.
> > > >> > >> > >
> > > >> > >> > > 7) DSL more extensive
> > > >> > >> > > The reifiers and DSL model is more extensive/expandable.
> For
> > > >> example a
> > > >> > >> > > new yaml dsl flow is developed at Camel K that required
> some of
> > > >> these
> > > >> > >> > > changes.
> > > >> > >> > >
> > > >> > >> > > 8) Properties component / placeholder
> > > >> > >> > > We can now easier extend this and also plugin to more 3rd
> > > >> parties such
> > > >> > >> > > as Eclipse MicroProfile Config (which is also needed by
> Camel
> > > >> Quarkus)
> > > >> > >> > >
> > > >> > >> > > 9) Usual stuff
> > > >> > >> > > Like bug fixes and whatnot.
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > I am currently working on getting the property component
> and
> > > >> > >> > > placeholder refactored so it works better and can easier to
> > > >> integrated
> > > >> > >> > > with other configuration libraries. Also it would allow us
> to
> > > >> > >> > > differentiate between read-only placeholders that can be
> loaded
> > > >> at
> > > >> > >> > > once, and others that are on-demand (eg to lookup in a
> database,
> > > >> > >> > > hashicorp vault etc.)
> > > >> > >> > >
> > > >> > >> > > Also the CI build server is now 100% passing for the last
> couple
> > > >> of
> > > >> > >> days.
> > > >> > >> > >
> > > >> > >> > > So lets see if we can get the last bits done by end of
> tomorrow
> > > >> or end
> > > >> > >> > > of next week, and get a RC cut.
> > > >> > >> > >
> > > >> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
> > > >> upgrade
> > > >> > >> and use.
> > > >> > >> > >
> > > >> > >> > > Any thoughts?
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > --
> > > >> > >> > > Claus Ibsen
> > > >> > >> > > -----------------
> > > >> > >> > > http://davsclaus.com @davsclaus
> > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >> > >>
> > > >> > >>
> > > >> > >>
> > > >> > >> --
> > > >> > >> Claus Ibsen
> > > >> > >> -----------------
> > > >> > >> http://davsclaus.com @davsclaus
> > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >> > >>
> > > >> > >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Claus Ibsen
> > > >> -----------------
> > > >> http://davsclaus.com @davsclaus
> > > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >>
> > > >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
Thanks a lot Gregor :-)
Il sab 6 lug 2019, 10:15 Gregor Zurowski <gr...@list.zurowski.org> ha
scritto:
> Hi Everyone:
>
> Thanks for making the changes to help prepare building the release
> candidate. I quickly validated the branch and it looks all good.
>
> I am now going to build the release candidate on a separate release
> branch. You can continue to apply changes to the master branch.
>
> Thanks,
> Gregor
>
> On Fri, Jul 5, 2019 at 7:34 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > On Fri, Jul 5, 2019 at 2:39 PM Andrea Cosentino <an...@gmail.com>
> wrote:
> > >
> > > By the way I don't see the half regen commit
> > >
> >
> > Ah yeah the push was reject as master was updated and I didnt spot
> > that before having to rush out the door.
> >
> > I finished the build and updated with a regen and set CS back to 250
> >
> > > Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <
> ancosen@gmail.com>
> > > ha scritto:
> > >
> > > > Enjoy the weekend :-)
> > > >
> > > > Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <
> > > > ancosen@gmail.com> ha scritto:
> > > >
> > > >> I'm on it
> > > >>
> > > >> Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <
> > > >> claus.ibsen@gmail.com> ha scritto:
> > > >>
> > > >>> Hi
> > > >>>
> > > >>> I gotta run out the door and have pushed a fix with half regen, can
> > > >>> you rebuild the rest and commit upstream
> > > >>>
> > > >>> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> > > >>> wrote:
> > > >>> >
> > > >>> > And when its committed you can set the line length back to 250
> > > >>> >
> > > >>> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <
> claus.ibsen@gmail.com>
> > > >>> wrote:
> > > >>> > >
> > > >>> > > Hi
> > > >>> > >
> > > >>> > > Thanks I got a word-wrap in the source code generate, will
> commit it
> > > >>> > > when it has regen the components
> > > >>> > >
> > > >>> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <
> ancosen@gmail.com>
> > > >>> wrote:
> > > >>> > > >
> > > >>> > > > Fixed.
> > > >>> > > >
> > > >>> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
> > > >>> ancosen@gmail.com>
> > > >>> > > > ha scritto:
> > > >>> > > >
> > > >>> > > > > We can override the property
> > > >>> > > > >
> > > >>> > > > >
> https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > > >>> > > > >
> > > >>> > > > > We can put 10000
> > > >>> > > > >
> > > >>> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
> > > >>> claus.ibsen@gmail.com>
> > > >>> > > > > ha scritto:
> > > >>> > > > >
> > > >>> > > > >> Hi
> > > >>> > > > >>
> > > >>> > > > >> Just a heads up that the checkstyle for endpoint-dsl will
> > > >>> report some
> > > >>> > > > >> errors
> > > >>> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > > >>> > > > >>
> > > >>> > > > >> As this is generated we cannot keep the source files
> below 5000
> > > >>> lines etc.
> > > >>> > > > >> And also some javadoc lines are long, as we would need to
> > > >>> word-wrap
> > > >>> > > > >> them ourselves
> > > >>> > > > >> to make this shorter.
> > > >>> > > > >>
> > > >>> > > > >> But I assume the RC can be cut anyway, just skip CS for
> this
> > > >>> module or in
> > > >>> > > > >> total.
> > > >>> > > > >>
> > > >>> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
> > > >>> ancosen@gmail.com>
> > > >>> > > > >> wrote:
> > > >>> > > > >> >
> > > >>> > > > >> > I've done with that documentation stuff. Gregor, when
> you are
> > > >>> available,
> > > >>> > > > >> > let us know.
> > > >>> > > > >> >
> > > >>> > > > >> > Thanks
> > > >>> > > > >> >
> > > >>> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea
> Cosentino <
> > > >>> > > > >> ancosen@gmail.com>
> > > >>> > > > >> > ha scritto:
> > > >>> > > > >> >
> > > >>> > > > >> > > I should finish a couple of things on the AWS
> components for
> > > >>> > > > >> documenting
> > > >>> > > > >> > > the region stuff. I should finish soon and send email
> > > >>> > > > >> > >
> > > >>> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > > >>> > > > >> claus.ibsen@gmail.com>
> > > >>> > > > >> > > ha scritto:
> > > >>> > > > >> > >
> > > >>> > > > >> > >> Hi
> > > >>> > > > >> > >>
> > > >>> > > > >> > >> I think the master branch is ready for a RC cut.
> > > >>> > > > >> > >>
> > > >>> > > > >> > >> Let us know if/when you get started Gregor
> > > >>> > > > >> > >>
> > > >>> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > > >>> > > > >> gregor@list.zurowski.org>
> > > >>> > > > >> > >> wrote:
> > > >>> > > > >> > >> >
> > > >>> > > > >> > >> > +1
> > > >>> > > > >> > >> >
> > > >>> > > > >> > >> > I'll be available for cutting the RC.
> > > >>> > > > >> > >> >
> > > >>> > > > >> > >> > Thanks,
> > > >>> > > > >> > >> > Gregor
> > > >>> > > > >> > >> >
> > > >>> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
> > > >>> claus.ibsen@gmail.com>
> > > >>> > > > >> > >> wrote:
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > Hi
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > I think we should close down on the last bits
> and get
> > > >>> milestone 4
> > > >>> > > > >> > >> > > released and in the hands to the community.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > We had a number of significant improvements and
> > > >>> features such as:
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 1) Endpoint DSL
> > > >>> > > > >> > >> > > Type safe fluent builder for configuring
> endpoints in
> > > >>> Java
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 2) Camel Main
> > > >>> > > > >> > >> > > Standalone Camel for microservices
> > > >>> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way
> to
> > > >>> bootstrap
> > > >>> > > > >> Camel
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 3) camel-core-engine
> > > >>> > > > >> > >> > > Tiny set of dependencies (only include
> absolutely what
> > > >>> you need)
> > > >>> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have
> smaller
> > > >>> set of JARs
> > > >>> > > > >> on
> > > >>> > > > >> > >> classpath
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 4) components depend on camel-support
> > > >>> > > > >> > >> > > Further reduced the dependency directly on
> camel-core
> > > >>> for all
> > > >>> > > > >> set of
> > > >>> > > > >> > >> > > components. To ensure we use
> camel-api/camel-support
> > > >>> for
> > > >>> > > > >> components
> > > >>> > > > >> > >> > > only.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 5) lazy start producer
> > > >>> > > > >> > >> > > You can configure in the endpoint that the
> producer
> > > >>> should lazy
> > > >>> > > > >> start
> > > >>> > > > >> > >> > > (eg on 1st message) you can use this to allow
> Camel to
> > > >>> startup
> > > >>> > > > >> even if
> > > >>> > > > >> > >> > > the producer would fail on startup - but now that
> > > >>> failure is
> > > >>> > > > >> deferred
> > > >>> > > > >> > >> > > to 1st message which you can then use Camels
> route
> > > >>> error handler
> > > >>> > > > >> to
> > > >>> > > > >> > >> > > deal with etc
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 6) SPI for Reactive Engine
> > > >>> > > > >> > >> > > So we can plugin a different engine such as Camel
> > > >>> Quarkus can
> > > >>> > > > >> benefit
> > > >>> > > > >> > >> > > from using its reactive engine.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 7) DSL more extensive
> > > >>> > > > >> > >> > > The reifiers and DSL model is more
> > > >>> extensive/expandable. For
> > > >>> > > > >> example a
> > > >>> > > > >> > >> > > new yaml dsl flow is developed at Camel K that
> > > >>> required some of
> > > >>> > > > >> these
> > > >>> > > > >> > >> > > changes.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 8) Properties component / placeholder
> > > >>> > > > >> > >> > > We can now easier extend this and also plugin to
> more
> > > >>> 3rd
> > > >>> > > > >> parties such
> > > >>> > > > >> > >> > > as Eclipse MicroProfile Config (which is also
> needed
> > > >>> by Camel
> > > >>> > > > >> Quarkus)
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > 9) Usual stuff
> > > >>> > > > >> > >> > > Like bug fixes and whatnot.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > I am currently working on getting the property
> > > >>> component and
> > > >>> > > > >> > >> > > placeholder refactored so it works better and can
> > > >>> easier to
> > > >>> > > > >> integrated
> > > >>> > > > >> > >> > > with other configuration libraries. Also it would
> > > >>> allow us to
> > > >>> > > > >> > >> > > differentiate between read-only placeholders
> that can
> > > >>> be loaded
> > > >>> > > > >> at
> > > >>> > > > >> > >> > > once, and others that are on-demand (eg to
> lookup in a
> > > >>> database,
> > > >>> > > > >> > >> > > hashicorp vault etc.)
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > Also the CI build server is now 100% passing for
> the
> > > >>> last couple
> > > >>> > > > >> of
> > > >>> > > > >> > >> days.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > So lets see if we can get the last bits done by
> end of
> > > >>> tomorrow
> > > >>> > > > >> or end
> > > >>> > > > >> > >> > > of next week, and get a RC cut.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > And we also need a M4 for both Camel K and Camel
> > > >>> Quarkus to
> > > >>> > > > >> upgrade
> > > >>> > > > >> > >> and use.
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > Any thoughts?
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > >
> > > >>> > > > >> > >> > > --
> > > >>> > > > >> > >> > > Claus Ibsen
> > > >>> > > > >> > >> > > -----------------
> > > >>> > > > >> > >> > > http://davsclaus.com @davsclaus
> > > >>> > > > >> > >> > > Camel in Action 2:
> https://www.manning.com/ibsen2
> > > >>> > > > >> > >>
> > > >>> > > > >> > >>
> > > >>> > > > >> > >>
> > > >>> > > > >> > >> --
> > > >>> > > > >> > >> Claus Ibsen
> > > >>> > > > >> > >> -----------------
> > > >>> > > > >> > >> http://davsclaus.com @davsclaus
> > > >>> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >>> > > > >> > >>
> > > >>> > > > >> > >
> > > >>> > > > >>
> > > >>> > > > >>
> > > >>> > > > >>
> > > >>> > > > >> --
> > > >>> > > > >> Claus Ibsen
> > > >>> > > > >> -----------------
> > > >>> > > > >> http://davsclaus.com @davsclaus
> > > >>> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >>> > > > >>
> > > >>> > > > >
> > > >>> > >
> > > >>> > >
> > > >>> > >
> > > >>> > > --
> > > >>> > > Claus Ibsen
> > > >>> > > -----------------
> > > >>> > > http://davsclaus.com @davsclaus
> > > >>> > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >>> >
> > > >>> >
> > > >>> >
> > > >>> > --
> > > >>> > Claus Ibsen
> > > >>> > -----------------
> > > >>> > http://davsclaus.com @davsclaus
> > > >>> > Camel in Action 2: https://www.manning.com/ibsen2
> > > >>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Claus Ibsen
> > > >>> -----------------
> > > >>> http://davsclaus.com @davsclaus
> > > >>> Camel in Action 2: https://www.manning.com/ibsen2
> > > >>>
> > > >>
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
Hi Everyone:
Thanks for making the changes to help prepare building the release
candidate. I quickly validated the branch and it looks all good.
I am now going to build the release candidate on a separate release
branch. You can continue to apply changes to the master branch.
Thanks,
Gregor
On Fri, Jul 5, 2019 at 7:34 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> On Fri, Jul 5, 2019 at 2:39 PM Andrea Cosentino <an...@gmail.com> wrote:
> >
> > By the way I don't see the half regen commit
> >
>
> Ah yeah the push was reject as master was updated and I didnt spot
> that before having to rush out the door.
>
> I finished the build and updated with a regen and set CS back to 250
>
> > Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <an...@gmail.com>
> > ha scritto:
> >
> > > Enjoy the weekend :-)
> > >
> > > Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <
> > > ancosen@gmail.com> ha scritto:
> > >
> > >> I'm on it
> > >>
> > >> Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <
> > >> claus.ibsen@gmail.com> ha scritto:
> > >>
> > >>> Hi
> > >>>
> > >>> I gotta run out the door and have pushed a fix with half regen, can
> > >>> you rebuild the rest and commit upstream
> > >>>
> > >>> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> > >>> wrote:
> > >>> >
> > >>> > And when its committed you can set the line length back to 250
> > >>> >
> > >>> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> > >>> wrote:
> > >>> > >
> > >>> > > Hi
> > >>> > >
> > >>> > > Thanks I got a word-wrap in the source code generate, will commit it
> > >>> > > when it has regen the components
> > >>> > >
> > >>> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
> > >>> wrote:
> > >>> > > >
> > >>> > > > Fixed.
> > >>> > > >
> > >>> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
> > >>> ancosen@gmail.com>
> > >>> > > > ha scritto:
> > >>> > > >
> > >>> > > > > We can override the property
> > >>> > > > >
> > >>> > > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > >>> > > > >
> > >>> > > > > We can put 10000
> > >>> > > > >
> > >>> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
> > >>> claus.ibsen@gmail.com>
> > >>> > > > > ha scritto:
> > >>> > > > >
> > >>> > > > >> Hi
> > >>> > > > >>
> > >>> > > > >> Just a heads up that the checkstyle for endpoint-dsl will
> > >>> report some
> > >>> > > > >> errors
> > >>> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > >>> > > > >>
> > >>> > > > >> As this is generated we cannot keep the source files below 5000
> > >>> lines etc.
> > >>> > > > >> And also some javadoc lines are long, as we would need to
> > >>> word-wrap
> > >>> > > > >> them ourselves
> > >>> > > > >> to make this shorter.
> > >>> > > > >>
> > >>> > > > >> But I assume the RC can be cut anyway, just skip CS for this
> > >>> module or in
> > >>> > > > >> total.
> > >>> > > > >>
> > >>> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
> > >>> ancosen@gmail.com>
> > >>> > > > >> wrote:
> > >>> > > > >> >
> > >>> > > > >> > I've done with that documentation stuff. Gregor, when you are
> > >>> available,
> > >>> > > > >> > let us know.
> > >>> > > > >> >
> > >>> > > > >> > Thanks
> > >>> > > > >> >
> > >>> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> > >>> > > > >> ancosen@gmail.com>
> > >>> > > > >> > ha scritto:
> > >>> > > > >> >
> > >>> > > > >> > > I should finish a couple of things on the AWS components for
> > >>> > > > >> documenting
> > >>> > > > >> > > the region stuff. I should finish soon and send email
> > >>> > > > >> > >
> > >>> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > >>> > > > >> claus.ibsen@gmail.com>
> > >>> > > > >> > > ha scritto:
> > >>> > > > >> > >
> > >>> > > > >> > >> Hi
> > >>> > > > >> > >>
> > >>> > > > >> > >> I think the master branch is ready for a RC cut.
> > >>> > > > >> > >>
> > >>> > > > >> > >> Let us know if/when you get started Gregor
> > >>> > > > >> > >>
> > >>> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > >>> > > > >> gregor@list.zurowski.org>
> > >>> > > > >> > >> wrote:
> > >>> > > > >> > >> >
> > >>> > > > >> > >> > +1
> > >>> > > > >> > >> >
> > >>> > > > >> > >> > I'll be available for cutting the RC.
> > >>> > > > >> > >> >
> > >>> > > > >> > >> > Thanks,
> > >>> > > > >> > >> > Gregor
> > >>> > > > >> > >> >
> > >>> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
> > >>> claus.ibsen@gmail.com>
> > >>> > > > >> > >> wrote:
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > Hi
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > I think we should close down on the last bits and get
> > >>> milestone 4
> > >>> > > > >> > >> > > released and in the hands to the community.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > We had a number of significant improvements and
> > >>> features such as:
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 1) Endpoint DSL
> > >>> > > > >> > >> > > Type safe fluent builder for configuring endpoints in
> > >>> Java
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 2) Camel Main
> > >>> > > > >> > >> > > Standalone Camel for microservices
> > >>> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
> > >>> bootstrap
> > >>> > > > >> Camel
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 3) camel-core-engine
> > >>> > > > >> > >> > > Tiny set of dependencies (only include absolutely what
> > >>> you need)
> > >>> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller
> > >>> set of JARs
> > >>> > > > >> on
> > >>> > > > >> > >> classpath
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 4) components depend on camel-support
> > >>> > > > >> > >> > > Further reduced the dependency directly on camel-core
> > >>> for all
> > >>> > > > >> set of
> > >>> > > > >> > >> > > components. To ensure we use camel-api/camel-support
> > >>> for
> > >>> > > > >> components
> > >>> > > > >> > >> > > only.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 5) lazy start producer
> > >>> > > > >> > >> > > You can configure in the endpoint that the producer
> > >>> should lazy
> > >>> > > > >> start
> > >>> > > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
> > >>> startup
> > >>> > > > >> even if
> > >>> > > > >> > >> > > the producer would fail on startup - but now that
> > >>> failure is
> > >>> > > > >> deferred
> > >>> > > > >> > >> > > to 1st message which you can then use Camels route
> > >>> error handler
> > >>> > > > >> to
> > >>> > > > >> > >> > > deal with etc
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 6) SPI for Reactive Engine
> > >>> > > > >> > >> > > So we can plugin a different engine such as Camel
> > >>> Quarkus can
> > >>> > > > >> benefit
> > >>> > > > >> > >> > > from using its reactive engine.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 7) DSL more extensive
> > >>> > > > >> > >> > > The reifiers and DSL model is more
> > >>> extensive/expandable. For
> > >>> > > > >> example a
> > >>> > > > >> > >> > > new yaml dsl flow is developed at Camel K that
> > >>> required some of
> > >>> > > > >> these
> > >>> > > > >> > >> > > changes.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 8) Properties component / placeholder
> > >>> > > > >> > >> > > We can now easier extend this and also plugin to more
> > >>> 3rd
> > >>> > > > >> parties such
> > >>> > > > >> > >> > > as Eclipse MicroProfile Config (which is also needed
> > >>> by Camel
> > >>> > > > >> Quarkus)
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > 9) Usual stuff
> > >>> > > > >> > >> > > Like bug fixes and whatnot.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > I am currently working on getting the property
> > >>> component and
> > >>> > > > >> > >> > > placeholder refactored so it works better and can
> > >>> easier to
> > >>> > > > >> integrated
> > >>> > > > >> > >> > > with other configuration libraries. Also it would
> > >>> allow us to
> > >>> > > > >> > >> > > differentiate between read-only placeholders that can
> > >>> be loaded
> > >>> > > > >> at
> > >>> > > > >> > >> > > once, and others that are on-demand (eg to lookup in a
> > >>> database,
> > >>> > > > >> > >> > > hashicorp vault etc.)
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > Also the CI build server is now 100% passing for the
> > >>> last couple
> > >>> > > > >> of
> > >>> > > > >> > >> days.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > So lets see if we can get the last bits done by end of
> > >>> tomorrow
> > >>> > > > >> or end
> > >>> > > > >> > >> > > of next week, and get a RC cut.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > And we also need a M4 for both Camel K and Camel
> > >>> Quarkus to
> > >>> > > > >> upgrade
> > >>> > > > >> > >> and use.
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > Any thoughts?
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > >
> > >>> > > > >> > >> > > --
> > >>> > > > >> > >> > > Claus Ibsen
> > >>> > > > >> > >> > > -----------------
> > >>> > > > >> > >> > > http://davsclaus.com @davsclaus
> > >>> > > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >>> > > > >> > >>
> > >>> > > > >> > >>
> > >>> > > > >> > >>
> > >>> > > > >> > >> --
> > >>> > > > >> > >> Claus Ibsen
> > >>> > > > >> > >> -----------------
> > >>> > > > >> > >> http://davsclaus.com @davsclaus
> > >>> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > >>> > > > >> > >>
> > >>> > > > >> > >
> > >>> > > > >>
> > >>> > > > >>
> > >>> > > > >>
> > >>> > > > >> --
> > >>> > > > >> Claus Ibsen
> > >>> > > > >> -----------------
> > >>> > > > >> http://davsclaus.com @davsclaus
> > >>> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
> > >>> > > > >>
> > >>> > > > >
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> > > --
> > >>> > > Claus Ibsen
> > >>> > > -----------------
> > >>> > > http://davsclaus.com @davsclaus
> > >>> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >>> >
> > >>> >
> > >>> >
> > >>> > --
> > >>> > Claus Ibsen
> > >>> > -----------------
> > >>> > http://davsclaus.com @davsclaus
> > >>> > Camel in Action 2: https://www.manning.com/ibsen2
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Claus Ibsen
> > >>> -----------------
> > >>> http://davsclaus.com @davsclaus
> > >>> Camel in Action 2: https://www.manning.com/ibsen2
> > >>>
> > >>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Jul 5, 2019 at 2:39 PM Andrea Cosentino <an...@gmail.com> wrote:
>
> By the way I don't see the half regen commit
>
Ah yeah the push was reject as master was updated and I didnt spot
that before having to rush out the door.
I finished the build and updated with a regen and set CS back to 250
> Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <an...@gmail.com>
> ha scritto:
>
> > Enjoy the weekend :-)
> >
> > Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <
> > ancosen@gmail.com> ha scritto:
> >
> >> I'm on it
> >>
> >> Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <
> >> claus.ibsen@gmail.com> ha scritto:
> >>
> >>> Hi
> >>>
> >>> I gotta run out the door and have pushed a fix with half regen, can
> >>> you rebuild the rest and commit upstream
> >>>
> >>> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> >>> wrote:
> >>> >
> >>> > And when its committed you can set the line length back to 250
> >>> >
> >>> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> >>> wrote:
> >>> > >
> >>> > > Hi
> >>> > >
> >>> > > Thanks I got a word-wrap in the source code generate, will commit it
> >>> > > when it has regen the components
> >>> > >
> >>> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
> >>> wrote:
> >>> > > >
> >>> > > > Fixed.
> >>> > > >
> >>> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
> >>> ancosen@gmail.com>
> >>> > > > ha scritto:
> >>> > > >
> >>> > > > > We can override the property
> >>> > > > >
> >>> > > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> >>> > > > >
> >>> > > > > We can put 10000
> >>> > > > >
> >>> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
> >>> claus.ibsen@gmail.com>
> >>> > > > > ha scritto:
> >>> > > > >
> >>> > > > >> Hi
> >>> > > > >>
> >>> > > > >> Just a heads up that the checkstyle for endpoint-dsl will
> >>> report some
> >>> > > > >> errors
> >>> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> >>> > > > >>
> >>> > > > >> As this is generated we cannot keep the source files below 5000
> >>> lines etc.
> >>> > > > >> And also some javadoc lines are long, as we would need to
> >>> word-wrap
> >>> > > > >> them ourselves
> >>> > > > >> to make this shorter.
> >>> > > > >>
> >>> > > > >> But I assume the RC can be cut anyway, just skip CS for this
> >>> module or in
> >>> > > > >> total.
> >>> > > > >>
> >>> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
> >>> ancosen@gmail.com>
> >>> > > > >> wrote:
> >>> > > > >> >
> >>> > > > >> > I've done with that documentation stuff. Gregor, when you are
> >>> available,
> >>> > > > >> > let us know.
> >>> > > > >> >
> >>> > > > >> > Thanks
> >>> > > > >> >
> >>> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> >>> > > > >> ancosen@gmail.com>
> >>> > > > >> > ha scritto:
> >>> > > > >> >
> >>> > > > >> > > I should finish a couple of things on the AWS components for
> >>> > > > >> documenting
> >>> > > > >> > > the region stuff. I should finish soon and send email
> >>> > > > >> > >
> >>> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> >>> > > > >> claus.ibsen@gmail.com>
> >>> > > > >> > > ha scritto:
> >>> > > > >> > >
> >>> > > > >> > >> Hi
> >>> > > > >> > >>
> >>> > > > >> > >> I think the master branch is ready for a RC cut.
> >>> > > > >> > >>
> >>> > > > >> > >> Let us know if/when you get started Gregor
> >>> > > > >> > >>
> >>> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> >>> > > > >> gregor@list.zurowski.org>
> >>> > > > >> > >> wrote:
> >>> > > > >> > >> >
> >>> > > > >> > >> > +1
> >>> > > > >> > >> >
> >>> > > > >> > >> > I'll be available for cutting the RC.
> >>> > > > >> > >> >
> >>> > > > >> > >> > Thanks,
> >>> > > > >> > >> > Gregor
> >>> > > > >> > >> >
> >>> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
> >>> claus.ibsen@gmail.com>
> >>> > > > >> > >> wrote:
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > Hi
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > I think we should close down on the last bits and get
> >>> milestone 4
> >>> > > > >> > >> > > released and in the hands to the community.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > We had a number of significant improvements and
> >>> features such as:
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 1) Endpoint DSL
> >>> > > > >> > >> > > Type safe fluent builder for configuring endpoints in
> >>> Java
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 2) Camel Main
> >>> > > > >> > >> > > Standalone Camel for microservices
> >>> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
> >>> bootstrap
> >>> > > > >> Camel
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 3) camel-core-engine
> >>> > > > >> > >> > > Tiny set of dependencies (only include absolutely what
> >>> you need)
> >>> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller
> >>> set of JARs
> >>> > > > >> on
> >>> > > > >> > >> classpath
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 4) components depend on camel-support
> >>> > > > >> > >> > > Further reduced the dependency directly on camel-core
> >>> for all
> >>> > > > >> set of
> >>> > > > >> > >> > > components. To ensure we use camel-api/camel-support
> >>> for
> >>> > > > >> components
> >>> > > > >> > >> > > only.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 5) lazy start producer
> >>> > > > >> > >> > > You can configure in the endpoint that the producer
> >>> should lazy
> >>> > > > >> start
> >>> > > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
> >>> startup
> >>> > > > >> even if
> >>> > > > >> > >> > > the producer would fail on startup - but now that
> >>> failure is
> >>> > > > >> deferred
> >>> > > > >> > >> > > to 1st message which you can then use Camels route
> >>> error handler
> >>> > > > >> to
> >>> > > > >> > >> > > deal with etc
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 6) SPI for Reactive Engine
> >>> > > > >> > >> > > So we can plugin a different engine such as Camel
> >>> Quarkus can
> >>> > > > >> benefit
> >>> > > > >> > >> > > from using its reactive engine.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 7) DSL more extensive
> >>> > > > >> > >> > > The reifiers and DSL model is more
> >>> extensive/expandable. For
> >>> > > > >> example a
> >>> > > > >> > >> > > new yaml dsl flow is developed at Camel K that
> >>> required some of
> >>> > > > >> these
> >>> > > > >> > >> > > changes.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 8) Properties component / placeholder
> >>> > > > >> > >> > > We can now easier extend this and also plugin to more
> >>> 3rd
> >>> > > > >> parties such
> >>> > > > >> > >> > > as Eclipse MicroProfile Config (which is also needed
> >>> by Camel
> >>> > > > >> Quarkus)
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > 9) Usual stuff
> >>> > > > >> > >> > > Like bug fixes and whatnot.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > I am currently working on getting the property
> >>> component and
> >>> > > > >> > >> > > placeholder refactored so it works better and can
> >>> easier to
> >>> > > > >> integrated
> >>> > > > >> > >> > > with other configuration libraries. Also it would
> >>> allow us to
> >>> > > > >> > >> > > differentiate between read-only placeholders that can
> >>> be loaded
> >>> > > > >> at
> >>> > > > >> > >> > > once, and others that are on-demand (eg to lookup in a
> >>> database,
> >>> > > > >> > >> > > hashicorp vault etc.)
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > Also the CI build server is now 100% passing for the
> >>> last couple
> >>> > > > >> of
> >>> > > > >> > >> days.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > So lets see if we can get the last bits done by end of
> >>> tomorrow
> >>> > > > >> or end
> >>> > > > >> > >> > > of next week, and get a RC cut.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > And we also need a M4 for both Camel K and Camel
> >>> Quarkus to
> >>> > > > >> upgrade
> >>> > > > >> > >> and use.
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > Any thoughts?
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > >
> >>> > > > >> > >> > > --
> >>> > > > >> > >> > > Claus Ibsen
> >>> > > > >> > >> > > -----------------
> >>> > > > >> > >> > > http://davsclaus.com @davsclaus
> >>> > > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> >>> > > > >> > >>
> >>> > > > >> > >>
> >>> > > > >> > >>
> >>> > > > >> > >> --
> >>> > > > >> > >> Claus Ibsen
> >>> > > > >> > >> -----------------
> >>> > > > >> > >> http://davsclaus.com @davsclaus
> >>> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> >>> > > > >> > >>
> >>> > > > >> > >
> >>> > > > >>
> >>> > > > >>
> >>> > > > >>
> >>> > > > >> --
> >>> > > > >> Claus Ibsen
> >>> > > > >> -----------------
> >>> > > > >> http://davsclaus.com @davsclaus
> >>> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
> >>> > > > >>
> >>> > > > >
> >>> > >
> >>> > >
> >>> > >
> >>> > > --
> >>> > > Claus Ibsen
> >>> > > -----------------
> >>> > > http://davsclaus.com @davsclaus
> >>> > > Camel in Action 2: https://www.manning.com/ibsen2
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Claus Ibsen
> >>> > -----------------
> >>> > http://davsclaus.com @davsclaus
> >>> > Camel in Action 2: https://www.manning.com/ibsen2
> >>>
> >>>
> >>>
> >>> --
> >>> Claus Ibsen
> >>> -----------------
> >>> http://davsclaus.com @davsclaus
> >>> Camel in Action 2: https://www.manning.com/ibsen2
> >>>
> >>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
By the way I don't see the half regen commit
Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <an...@gmail.com>
ha scritto:
> Enjoy the weekend :-)
>
> Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <
> ancosen@gmail.com> ha scritto:
>
>> I'm on it
>>
>> Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <
>> claus.ibsen@gmail.com> ha scritto:
>>
>>> Hi
>>>
>>> I gotta run out the door and have pushed a fix with half regen, can
>>> you rebuild the rest and commit upstream
>>>
>>> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
>>> wrote:
>>> >
>>> > And when its committed you can set the line length back to 250
>>> >
>>> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
>>> wrote:
>>> > >
>>> > > Hi
>>> > >
>>> > > Thanks I got a word-wrap in the source code generate, will commit it
>>> > > when it has regen the components
>>> > >
>>> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
>>> wrote:
>>> > > >
>>> > > > Fixed.
>>> > > >
>>> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
>>> ancosen@gmail.com>
>>> > > > ha scritto:
>>> > > >
>>> > > > > We can override the property
>>> > > > >
>>> > > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
>>> > > > >
>>> > > > > We can put 10000
>>> > > > >
>>> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
>>> claus.ibsen@gmail.com>
>>> > > > > ha scritto:
>>> > > > >
>>> > > > >> Hi
>>> > > > >>
>>> > > > >> Just a heads up that the checkstyle for endpoint-dsl will
>>> report some
>>> > > > >> errors
>>> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
>>> > > > >>
>>> > > > >> As this is generated we cannot keep the source files below 5000
>>> lines etc.
>>> > > > >> And also some javadoc lines are long, as we would need to
>>> word-wrap
>>> > > > >> them ourselves
>>> > > > >> to make this shorter.
>>> > > > >>
>>> > > > >> But I assume the RC can be cut anyway, just skip CS for this
>>> module or in
>>> > > > >> total.
>>> > > > >>
>>> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
>>> ancosen@gmail.com>
>>> > > > >> wrote:
>>> > > > >> >
>>> > > > >> > I've done with that documentation stuff. Gregor, when you are
>>> available,
>>> > > > >> > let us know.
>>> > > > >> >
>>> > > > >> > Thanks
>>> > > > >> >
>>> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
>>> > > > >> ancosen@gmail.com>
>>> > > > >> > ha scritto:
>>> > > > >> >
>>> > > > >> > > I should finish a couple of things on the AWS components for
>>> > > > >> documenting
>>> > > > >> > > the region stuff. I should finish soon and send email
>>> > > > >> > >
>>> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
>>> > > > >> claus.ibsen@gmail.com>
>>> > > > >> > > ha scritto:
>>> > > > >> > >
>>> > > > >> > >> Hi
>>> > > > >> > >>
>>> > > > >> > >> I think the master branch is ready for a RC cut.
>>> > > > >> > >>
>>> > > > >> > >> Let us know if/when you get started Gregor
>>> > > > >> > >>
>>> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
>>> > > > >> gregor@list.zurowski.org>
>>> > > > >> > >> wrote:
>>> > > > >> > >> >
>>> > > > >> > >> > +1
>>> > > > >> > >> >
>>> > > > >> > >> > I'll be available for cutting the RC.
>>> > > > >> > >> >
>>> > > > >> > >> > Thanks,
>>> > > > >> > >> > Gregor
>>> > > > >> > >> >
>>> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
>>> claus.ibsen@gmail.com>
>>> > > > >> > >> wrote:
>>> > > > >> > >> > >
>>> > > > >> > >> > > Hi
>>> > > > >> > >> > >
>>> > > > >> > >> > > I think we should close down on the last bits and get
>>> milestone 4
>>> > > > >> > >> > > released and in the hands to the community.
>>> > > > >> > >> > >
>>> > > > >> > >> > > We had a number of significant improvements and
>>> features such as:
>>> > > > >> > >> > >
>>> > > > >> > >> > > 1) Endpoint DSL
>>> > > > >> > >> > > Type safe fluent builder for configuring endpoints in
>>> Java
>>> > > > >> > >> > >
>>> > > > >> > >> > > 2) Camel Main
>>> > > > >> > >> > > Standalone Camel for microservices
>>> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
>>> bootstrap
>>> > > > >> Camel
>>> > > > >> > >> > >
>>> > > > >> > >> > > 3) camel-core-engine
>>> > > > >> > >> > > Tiny set of dependencies (only include absolutely what
>>> you need)
>>> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller
>>> set of JARs
>>> > > > >> on
>>> > > > >> > >> classpath
>>> > > > >> > >> > >
>>> > > > >> > >> > > 4) components depend on camel-support
>>> > > > >> > >> > > Further reduced the dependency directly on camel-core
>>> for all
>>> > > > >> set of
>>> > > > >> > >> > > components. To ensure we use camel-api/camel-support
>>> for
>>> > > > >> components
>>> > > > >> > >> > > only.
>>> > > > >> > >> > >
>>> > > > >> > >> > > 5) lazy start producer
>>> > > > >> > >> > > You can configure in the endpoint that the producer
>>> should lazy
>>> > > > >> start
>>> > > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
>>> startup
>>> > > > >> even if
>>> > > > >> > >> > > the producer would fail on startup - but now that
>>> failure is
>>> > > > >> deferred
>>> > > > >> > >> > > to 1st message which you can then use Camels route
>>> error handler
>>> > > > >> to
>>> > > > >> > >> > > deal with etc
>>> > > > >> > >> > >
>>> > > > >> > >> > > 6) SPI for Reactive Engine
>>> > > > >> > >> > > So we can plugin a different engine such as Camel
>>> Quarkus can
>>> > > > >> benefit
>>> > > > >> > >> > > from using its reactive engine.
>>> > > > >> > >> > >
>>> > > > >> > >> > > 7) DSL more extensive
>>> > > > >> > >> > > The reifiers and DSL model is more
>>> extensive/expandable. For
>>> > > > >> example a
>>> > > > >> > >> > > new yaml dsl flow is developed at Camel K that
>>> required some of
>>> > > > >> these
>>> > > > >> > >> > > changes.
>>> > > > >> > >> > >
>>> > > > >> > >> > > 8) Properties component / placeholder
>>> > > > >> > >> > > We can now easier extend this and also plugin to more
>>> 3rd
>>> > > > >> parties such
>>> > > > >> > >> > > as Eclipse MicroProfile Config (which is also needed
>>> by Camel
>>> > > > >> Quarkus)
>>> > > > >> > >> > >
>>> > > > >> > >> > > 9) Usual stuff
>>> > > > >> > >> > > Like bug fixes and whatnot.
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > > I am currently working on getting the property
>>> component and
>>> > > > >> > >> > > placeholder refactored so it works better and can
>>> easier to
>>> > > > >> integrated
>>> > > > >> > >> > > with other configuration libraries. Also it would
>>> allow us to
>>> > > > >> > >> > > differentiate between read-only placeholders that can
>>> be loaded
>>> > > > >> at
>>> > > > >> > >> > > once, and others that are on-demand (eg to lookup in a
>>> database,
>>> > > > >> > >> > > hashicorp vault etc.)
>>> > > > >> > >> > >
>>> > > > >> > >> > > Also the CI build server is now 100% passing for the
>>> last couple
>>> > > > >> of
>>> > > > >> > >> days.
>>> > > > >> > >> > >
>>> > > > >> > >> > > So lets see if we can get the last bits done by end of
>>> tomorrow
>>> > > > >> or end
>>> > > > >> > >> > > of next week, and get a RC cut.
>>> > > > >> > >> > >
>>> > > > >> > >> > > And we also need a M4 for both Camel K and Camel
>>> Quarkus to
>>> > > > >> upgrade
>>> > > > >> > >> and use.
>>> > > > >> > >> > >
>>> > > > >> > >> > > Any thoughts?
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > >
>>> > > > >> > >> > > --
>>> > > > >> > >> > > Claus Ibsen
>>> > > > >> > >> > > -----------------
>>> > > > >> > >> > > http://davsclaus.com @davsclaus
>>> > > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
>>> > > > >> > >>
>>> > > > >> > >>
>>> > > > >> > >>
>>> > > > >> > >> --
>>> > > > >> > >> Claus Ibsen
>>> > > > >> > >> -----------------
>>> > > > >> > >> http://davsclaus.com @davsclaus
>>> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
>>> > > > >> > >>
>>> > > > >> > >
>>> > > > >>
>>> > > > >>
>>> > > > >>
>>> > > > >> --
>>> > > > >> Claus Ibsen
>>> > > > >> -----------------
>>> > > > >> http://davsclaus.com @davsclaus
>>> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
>>> > > > >>
>>> > > > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Claus Ibsen
>>> > > -----------------
>>> > > http://davsclaus.com @davsclaus
>>> > > Camel in Action 2: https://www.manning.com/ibsen2
>>> >
>>> >
>>> >
>>> > --
>>> > Claus Ibsen
>>> > -----------------
>>> > http://davsclaus.com @davsclaus
>>> > Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
Enjoy the weekend :-)
Il giorno ven 5 lug 2019 alle ore 14:38 Andrea Cosentino <an...@gmail.com>
ha scritto:
> I'm on it
>
> Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <cl...@gmail.com>
> ha scritto:
>
>> Hi
>>
>> I gotta run out the door and have pushed a fix with half regen, can
>> you rebuild the rest and commit upstream
>>
>> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
>> >
>> > And when its committed you can set the line length back to 250
>> >
>> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
>> wrote:
>> > >
>> > > Hi
>> > >
>> > > Thanks I got a word-wrap in the source code generate, will commit it
>> > > when it has regen the components
>> > >
>> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
>> wrote:
>> > > >
>> > > > Fixed.
>> > > >
>> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
>> ancosen@gmail.com>
>> > > > ha scritto:
>> > > >
>> > > > > We can override the property
>> > > > >
>> > > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
>> > > > >
>> > > > > We can put 10000
>> > > > >
>> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
>> claus.ibsen@gmail.com>
>> > > > > ha scritto:
>> > > > >
>> > > > >> Hi
>> > > > >>
>> > > > >> Just a heads up that the checkstyle for endpoint-dsl will report
>> some
>> > > > >> errors
>> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
>> > > > >>
>> > > > >> As this is generated we cannot keep the source files below 5000
>> lines etc.
>> > > > >> And also some javadoc lines are long, as we would need to
>> word-wrap
>> > > > >> them ourselves
>> > > > >> to make this shorter.
>> > > > >>
>> > > > >> But I assume the RC can be cut anyway, just skip CS for this
>> module or in
>> > > > >> total.
>> > > > >>
>> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
>> ancosen@gmail.com>
>> > > > >> wrote:
>> > > > >> >
>> > > > >> > I've done with that documentation stuff. Gregor, when you are
>> available,
>> > > > >> > let us know.
>> > > > >> >
>> > > > >> > Thanks
>> > > > >> >
>> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
>> > > > >> ancosen@gmail.com>
>> > > > >> > ha scritto:
>> > > > >> >
>> > > > >> > > I should finish a couple of things on the AWS components for
>> > > > >> documenting
>> > > > >> > > the region stuff. I should finish soon and send email
>> > > > >> > >
>> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
>> > > > >> claus.ibsen@gmail.com>
>> > > > >> > > ha scritto:
>> > > > >> > >
>> > > > >> > >> Hi
>> > > > >> > >>
>> > > > >> > >> I think the master branch is ready for a RC cut.
>> > > > >> > >>
>> > > > >> > >> Let us know if/when you get started Gregor
>> > > > >> > >>
>> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
>> > > > >> gregor@list.zurowski.org>
>> > > > >> > >> wrote:
>> > > > >> > >> >
>> > > > >> > >> > +1
>> > > > >> > >> >
>> > > > >> > >> > I'll be available for cutting the RC.
>> > > > >> > >> >
>> > > > >> > >> > Thanks,
>> > > > >> > >> > Gregor
>> > > > >> > >> >
>> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
>> claus.ibsen@gmail.com>
>> > > > >> > >> wrote:
>> > > > >> > >> > >
>> > > > >> > >> > > Hi
>> > > > >> > >> > >
>> > > > >> > >> > > I think we should close down on the last bits and get
>> milestone 4
>> > > > >> > >> > > released and in the hands to the community.
>> > > > >> > >> > >
>> > > > >> > >> > > We had a number of significant improvements and
>> features such as:
>> > > > >> > >> > >
>> > > > >> > >> > > 1) Endpoint DSL
>> > > > >> > >> > > Type safe fluent builder for configuring endpoints in
>> Java
>> > > > >> > >> > >
>> > > > >> > >> > > 2) Camel Main
>> > > > >> > >> > > Standalone Camel for microservices
>> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
>> bootstrap
>> > > > >> Camel
>> > > > >> > >> > >
>> > > > >> > >> > > 3) camel-core-engine
>> > > > >> > >> > > Tiny set of dependencies (only include absolutely what
>> you need)
>> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set
>> of JARs
>> > > > >> on
>> > > > >> > >> classpath
>> > > > >> > >> > >
>> > > > >> > >> > > 4) components depend on camel-support
>> > > > >> > >> > > Further reduced the dependency directly on camel-core
>> for all
>> > > > >> set of
>> > > > >> > >> > > components. To ensure we use camel-api/camel-support for
>> > > > >> components
>> > > > >> > >> > > only.
>> > > > >> > >> > >
>> > > > >> > >> > > 5) lazy start producer
>> > > > >> > >> > > You can configure in the endpoint that the producer
>> should lazy
>> > > > >> start
>> > > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
>> startup
>> > > > >> even if
>> > > > >> > >> > > the producer would fail on startup - but now that
>> failure is
>> > > > >> deferred
>> > > > >> > >> > > to 1st message which you can then use Camels route
>> error handler
>> > > > >> to
>> > > > >> > >> > > deal with etc
>> > > > >> > >> > >
>> > > > >> > >> > > 6) SPI for Reactive Engine
>> > > > >> > >> > > So we can plugin a different engine such as Camel
>> Quarkus can
>> > > > >> benefit
>> > > > >> > >> > > from using its reactive engine.
>> > > > >> > >> > >
>> > > > >> > >> > > 7) DSL more extensive
>> > > > >> > >> > > The reifiers and DSL model is more
>> extensive/expandable. For
>> > > > >> example a
>> > > > >> > >> > > new yaml dsl flow is developed at Camel K that required
>> some of
>> > > > >> these
>> > > > >> > >> > > changes.
>> > > > >> > >> > >
>> > > > >> > >> > > 8) Properties component / placeholder
>> > > > >> > >> > > We can now easier extend this and also plugin to more
>> 3rd
>> > > > >> parties such
>> > > > >> > >> > > as Eclipse MicroProfile Config (which is also needed by
>> Camel
>> > > > >> Quarkus)
>> > > > >> > >> > >
>> > > > >> > >> > > 9) Usual stuff
>> > > > >> > >> > > Like bug fixes and whatnot.
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > > I am currently working on getting the property
>> component and
>> > > > >> > >> > > placeholder refactored so it works better and can
>> easier to
>> > > > >> integrated
>> > > > >> > >> > > with other configuration libraries. Also it would allow
>> us to
>> > > > >> > >> > > differentiate between read-only placeholders that can
>> be loaded
>> > > > >> at
>> > > > >> > >> > > once, and others that are on-demand (eg to lookup in a
>> database,
>> > > > >> > >> > > hashicorp vault etc.)
>> > > > >> > >> > >
>> > > > >> > >> > > Also the CI build server is now 100% passing for the
>> last couple
>> > > > >> of
>> > > > >> > >> days.
>> > > > >> > >> > >
>> > > > >> > >> > > So lets see if we can get the last bits done by end of
>> tomorrow
>> > > > >> or end
>> > > > >> > >> > > of next week, and get a RC cut.
>> > > > >> > >> > >
>> > > > >> > >> > > And we also need a M4 for both Camel K and Camel
>> Quarkus to
>> > > > >> upgrade
>> > > > >> > >> and use.
>> > > > >> > >> > >
>> > > > >> > >> > > Any thoughts?
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > > --
>> > > > >> > >> > > Claus Ibsen
>> > > > >> > >> > > -----------------
>> > > > >> > >> > > http://davsclaus.com @davsclaus
>> > > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
>> > > > >> > >>
>> > > > >> > >>
>> > > > >> > >>
>> > > > >> > >> --
>> > > > >> > >> Claus Ibsen
>> > > > >> > >> -----------------
>> > > > >> > >> http://davsclaus.com @davsclaus
>> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
>> > > > >> > >>
>> > > > >> > >
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >> Claus Ibsen
>> > > > >> -----------------
>> > > > >> http://davsclaus.com @davsclaus
>> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
>> > > > >>
>> > > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Claus Ibsen
>> > > -----------------
>> > > http://davsclaus.com @davsclaus
>> > > Camel in Action 2: https://www.manning.com/ibsen2
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
I'm on it
Il giorno ven 5 lug 2019 alle ore 14:37 Claus Ibsen <cl...@gmail.com>
ha scritto:
> Hi
>
> I gotta run out the door and have pushed a fix with half regen, can
> you rebuild the rest and commit upstream
>
> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > And when its committed you can set the line length back to 250
> >
> > On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com>
> wrote:
> > >
> > > Hi
> > >
> > > Thanks I got a word-wrap in the source code generate, will commit it
> > > when it has regen the components
> > >
> > > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com>
> wrote:
> > > >
> > > > Fixed.
> > > >
> > > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <
> ancosen@gmail.com>
> > > > ha scritto:
> > > >
> > > > > We can override the property
> > > > >
> > > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > > > >
> > > > > We can put 10000
> > > > >
> > > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <
> claus.ibsen@gmail.com>
> > > > > ha scritto:
> > > > >
> > > > >> Hi
> > > > >>
> > > > >> Just a heads up that the checkstyle for endpoint-dsl will report
> some
> > > > >> errors
> > > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > > > >>
> > > > >> As this is generated we cannot keep the source files below 5000
> lines etc.
> > > > >> And also some javadoc lines are long, as we would need to
> word-wrap
> > > > >> them ourselves
> > > > >> to make this shorter.
> > > > >>
> > > > >> But I assume the RC can be cut anyway, just skip CS for this
> module or in
> > > > >> total.
> > > > >>
> > > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <
> ancosen@gmail.com>
> > > > >> wrote:
> > > > >> >
> > > > >> > I've done with that documentation stuff. Gregor, when you are
> available,
> > > > >> > let us know.
> > > > >> >
> > > > >> > Thanks
> > > > >> >
> > > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> > > > >> ancosen@gmail.com>
> > > > >> > ha scritto:
> > > > >> >
> > > > >> > > I should finish a couple of things on the AWS components for
> > > > >> documenting
> > > > >> > > the region stuff. I should finish soon and send email
> > > > >> > >
> > > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > > > >> claus.ibsen@gmail.com>
> > > > >> > > ha scritto:
> > > > >> > >
> > > > >> > >> Hi
> > > > >> > >>
> > > > >> > >> I think the master branch is ready for a RC cut.
> > > > >> > >>
> > > > >> > >> Let us know if/when you get started Gregor
> > > > >> > >>
> > > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > > > >> gregor@list.zurowski.org>
> > > > >> > >> wrote:
> > > > >> > >> >
> > > > >> > >> > +1
> > > > >> > >> >
> > > > >> > >> > I'll be available for cutting the RC.
> > > > >> > >> >
> > > > >> > >> > Thanks,
> > > > >> > >> > Gregor
> > > > >> > >> >
> > > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <
> claus.ibsen@gmail.com>
> > > > >> > >> wrote:
> > > > >> > >> > >
> > > > >> > >> > > Hi
> > > > >> > >> > >
> > > > >> > >> > > I think we should close down on the last bits and get
> milestone 4
> > > > >> > >> > > released and in the hands to the community.
> > > > >> > >> > >
> > > > >> > >> > > We had a number of significant improvements and features
> such as:
> > > > >> > >> > >
> > > > >> > >> > > 1) Endpoint DSL
> > > > >> > >> > > Type safe fluent builder for configuring endpoints in
> Java
> > > > >> > >> > >
> > > > >> > >> > > 2) Camel Main
> > > > >> > >> > > Standalone Camel for microservices
> > > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to
> bootstrap
> > > > >> Camel
> > > > >> > >> > >
> > > > >> > >> > > 3) camel-core-engine
> > > > >> > >> > > Tiny set of dependencies (only include absolutely what
> you need)
> > > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set
> of JARs
> > > > >> on
> > > > >> > >> classpath
> > > > >> > >> > >
> > > > >> > >> > > 4) components depend on camel-support
> > > > >> > >> > > Further reduced the dependency directly on camel-core
> for all
> > > > >> set of
> > > > >> > >> > > components. To ensure we use camel-api/camel-support for
> > > > >> components
> > > > >> > >> > > only.
> > > > >> > >> > >
> > > > >> > >> > > 5) lazy start producer
> > > > >> > >> > > You can configure in the endpoint that the producer
> should lazy
> > > > >> start
> > > > >> > >> > > (eg on 1st message) you can use this to allow Camel to
> startup
> > > > >> even if
> > > > >> > >> > > the producer would fail on startup - but now that
> failure is
> > > > >> deferred
> > > > >> > >> > > to 1st message which you can then use Camels route error
> handler
> > > > >> to
> > > > >> > >> > > deal with etc
> > > > >> > >> > >
> > > > >> > >> > > 6) SPI for Reactive Engine
> > > > >> > >> > > So we can plugin a different engine such as Camel
> Quarkus can
> > > > >> benefit
> > > > >> > >> > > from using its reactive engine.
> > > > >> > >> > >
> > > > >> > >> > > 7) DSL more extensive
> > > > >> > >> > > The reifiers and DSL model is more extensive/expandable.
> For
> > > > >> example a
> > > > >> > >> > > new yaml dsl flow is developed at Camel K that required
> some of
> > > > >> these
> > > > >> > >> > > changes.
> > > > >> > >> > >
> > > > >> > >> > > 8) Properties component / placeholder
> > > > >> > >> > > We can now easier extend this and also plugin to more 3rd
> > > > >> parties such
> > > > >> > >> > > as Eclipse MicroProfile Config (which is also needed by
> Camel
> > > > >> Quarkus)
> > > > >> > >> > >
> > > > >> > >> > > 9) Usual stuff
> > > > >> > >> > > Like bug fixes and whatnot.
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > I am currently working on getting the property component
> and
> > > > >> > >> > > placeholder refactored so it works better and can easier
> to
> > > > >> integrated
> > > > >> > >> > > with other configuration libraries. Also it would allow
> us to
> > > > >> > >> > > differentiate between read-only placeholders that can be
> loaded
> > > > >> at
> > > > >> > >> > > once, and others that are on-demand (eg to lookup in a
> database,
> > > > >> > >> > > hashicorp vault etc.)
> > > > >> > >> > >
> > > > >> > >> > > Also the CI build server is now 100% passing for the
> last couple
> > > > >> of
> > > > >> > >> days.
> > > > >> > >> > >
> > > > >> > >> > > So lets see if we can get the last bits done by end of
> tomorrow
> > > > >> or end
> > > > >> > >> > > of next week, and get a RC cut.
> > > > >> > >> > >
> > > > >> > >> > > And we also need a M4 for both Camel K and Camel Quarkus
> to
> > > > >> upgrade
> > > > >> > >> and use.
> > > > >> > >> > >
> > > > >> > >> > > Any thoughts?
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > --
> > > > >> > >> > > Claus Ibsen
> > > > >> > >> > > -----------------
> > > > >> > >> > > http://davsclaus.com @davsclaus
> > > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > >> > >>
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> --
> > > > >> > >> Claus Ibsen
> > > > >> > >> -----------------
> > > > >> > >> http://davsclaus.com @davsclaus
> > > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > > >> > >>
> > > > >> > >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Claus Ibsen
> > > > >> -----------------
> > > > >> http://davsclaus.com @davsclaus
> > > > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > > >>
> > > > >
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I gotta run out the door and have pushed a fix with half regen, can
you rebuild the rest and commit upstream
On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> And when its committed you can set the line length back to 250
>
> On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > Thanks I got a word-wrap in the source code generate, will commit it
> > when it has regen the components
> >
> > On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com> wrote:
> > >
> > > Fixed.
> > >
> > > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <an...@gmail.com>
> > > ha scritto:
> > >
> > > > We can override the property
> > > >
> > > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > > >
> > > > We can put 10000
> > > >
> > > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <cl...@gmail.com>
> > > > ha scritto:
> > > >
> > > >> Hi
> > > >>
> > > >> Just a heads up that the checkstyle for endpoint-dsl will report some
> > > >> errors
> > > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > > >>
> > > >> As this is generated we cannot keep the source files below 5000 lines etc.
> > > >> And also some javadoc lines are long, as we would need to word-wrap
> > > >> them ourselves
> > > >> to make this shorter.
> > > >>
> > > >> But I assume the RC can be cut anyway, just skip CS for this module or in
> > > >> total.
> > > >>
> > > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com>
> > > >> wrote:
> > > >> >
> > > >> > I've done with that documentation stuff. Gregor, when you are available,
> > > >> > let us know.
> > > >> >
> > > >> > Thanks
> > > >> >
> > > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> > > >> ancosen@gmail.com>
> > > >> > ha scritto:
> > > >> >
> > > >> > > I should finish a couple of things on the AWS components for
> > > >> documenting
> > > >> > > the region stuff. I should finish soon and send email
> > > >> > >
> > > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > > >> claus.ibsen@gmail.com>
> > > >> > > ha scritto:
> > > >> > >
> > > >> > >> Hi
> > > >> > >>
> > > >> > >> I think the master branch is ready for a RC cut.
> > > >> > >>
> > > >> > >> Let us know if/when you get started Gregor
> > > >> > >>
> > > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > > >> gregor@list.zurowski.org>
> > > >> > >> wrote:
> > > >> > >> >
> > > >> > >> > +1
> > > >> > >> >
> > > >> > >> > I'll be available for cutting the RC.
> > > >> > >> >
> > > >> > >> > Thanks,
> > > >> > >> > Gregor
> > > >> > >> >
> > > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> > > >> > >> wrote:
> > > >> > >> > >
> > > >> > >> > > Hi
> > > >> > >> > >
> > > >> > >> > > I think we should close down on the last bits and get milestone 4
> > > >> > >> > > released and in the hands to the community.
> > > >> > >> > >
> > > >> > >> > > We had a number of significant improvements and features such as:
> > > >> > >> > >
> > > >> > >> > > 1) Endpoint DSL
> > > >> > >> > > Type safe fluent builder for configuring endpoints in Java
> > > >> > >> > >
> > > >> > >> > > 2) Camel Main
> > > >> > >> > > Standalone Camel for microservices
> > > >> > >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap
> > > >> Camel
> > > >> > >> > >
> > > >> > >> > > 3) camel-core-engine
> > > >> > >> > > Tiny set of dependencies (only include absolutely what you need)
> > > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs
> > > >> on
> > > >> > >> classpath
> > > >> > >> > >
> > > >> > >> > > 4) components depend on camel-support
> > > >> > >> > > Further reduced the dependency directly on camel-core for all
> > > >> set of
> > > >> > >> > > components. To ensure we use camel-api/camel-support for
> > > >> components
> > > >> > >> > > only.
> > > >> > >> > >
> > > >> > >> > > 5) lazy start producer
> > > >> > >> > > You can configure in the endpoint that the producer should lazy
> > > >> start
> > > >> > >> > > (eg on 1st message) you can use this to allow Camel to startup
> > > >> even if
> > > >> > >> > > the producer would fail on startup - but now that failure is
> > > >> deferred
> > > >> > >> > > to 1st message which you can then use Camels route error handler
> > > >> to
> > > >> > >> > > deal with etc
> > > >> > >> > >
> > > >> > >> > > 6) SPI for Reactive Engine
> > > >> > >> > > So we can plugin a different engine such as Camel Quarkus can
> > > >> benefit
> > > >> > >> > > from using its reactive engine.
> > > >> > >> > >
> > > >> > >> > > 7) DSL more extensive
> > > >> > >> > > The reifiers and DSL model is more extensive/expandable. For
> > > >> example a
> > > >> > >> > > new yaml dsl flow is developed at Camel K that required some of
> > > >> these
> > > >> > >> > > changes.
> > > >> > >> > >
> > > >> > >> > > 8) Properties component / placeholder
> > > >> > >> > > We can now easier extend this and also plugin to more 3rd
> > > >> parties such
> > > >> > >> > > as Eclipse MicroProfile Config (which is also needed by Camel
> > > >> Quarkus)
> > > >> > >> > >
> > > >> > >> > > 9) Usual stuff
> > > >> > >> > > Like bug fixes and whatnot.
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > I am currently working on getting the property component and
> > > >> > >> > > placeholder refactored so it works better and can easier to
> > > >> integrated
> > > >> > >> > > with other configuration libraries. Also it would allow us to
> > > >> > >> > > differentiate between read-only placeholders that can be loaded
> > > >> at
> > > >> > >> > > once, and others that are on-demand (eg to lookup in a database,
> > > >> > >> > > hashicorp vault etc.)
> > > >> > >> > >
> > > >> > >> > > Also the CI build server is now 100% passing for the last couple
> > > >> of
> > > >> > >> days.
> > > >> > >> > >
> > > >> > >> > > So lets see if we can get the last bits done by end of tomorrow
> > > >> or end
> > > >> > >> > > of next week, and get a RC cut.
> > > >> > >> > >
> > > >> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
> > > >> upgrade
> > > >> > >> and use.
> > > >> > >> > >
> > > >> > >> > > Any thoughts?
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > --
> > > >> > >> > > Claus Ibsen
> > > >> > >> > > -----------------
> > > >> > >> > > http://davsclaus.com @davsclaus
> > > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >> > >>
> > > >> > >>
> > > >> > >>
> > > >> > >> --
> > > >> > >> Claus Ibsen
> > > >> > >> -----------------
> > > >> > >> http://davsclaus.com @davsclaus
> > > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >> > >>
> > > >> > >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Claus Ibsen
> > > >> -----------------
> > > >> http://davsclaus.com @davsclaus
> > > >> Camel in Action 2: https://www.manning.com/ibsen2
> > > >>
> > > >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
And when its committed you can set the line length back to 250
On Fri, Jul 5, 2019 at 2:34 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> Thanks I got a word-wrap in the source code generate, will commit it
> when it has regen the components
>
> On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com> wrote:
> >
> > Fixed.
> >
> > Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <an...@gmail.com>
> > ha scritto:
> >
> > > We can override the property
> > >
> > > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> > >
> > > We can put 10000
> > >
> > > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <cl...@gmail.com>
> > > ha scritto:
> > >
> > >> Hi
> > >>
> > >> Just a heads up that the checkstyle for endpoint-dsl will report some
> > >> errors
> > >> https://issues.apache.org/jira/browse/CAMEL-13728
> > >>
> > >> As this is generated we cannot keep the source files below 5000 lines etc.
> > >> And also some javadoc lines are long, as we would need to word-wrap
> > >> them ourselves
> > >> to make this shorter.
> > >>
> > >> But I assume the RC can be cut anyway, just skip CS for this module or in
> > >> total.
> > >>
> > >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com>
> > >> wrote:
> > >> >
> > >> > I've done with that documentation stuff. Gregor, when you are available,
> > >> > let us know.
> > >> >
> > >> > Thanks
> > >> >
> > >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> > >> ancosen@gmail.com>
> > >> > ha scritto:
> > >> >
> > >> > > I should finish a couple of things on the AWS components for
> > >> documenting
> > >> > > the region stuff. I should finish soon and send email
> > >> > >
> > >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> > >> claus.ibsen@gmail.com>
> > >> > > ha scritto:
> > >> > >
> > >> > >> Hi
> > >> > >>
> > >> > >> I think the master branch is ready for a RC cut.
> > >> > >>
> > >> > >> Let us know if/when you get started Gregor
> > >> > >>
> > >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> > >> gregor@list.zurowski.org>
> > >> > >> wrote:
> > >> > >> >
> > >> > >> > +1
> > >> > >> >
> > >> > >> > I'll be available for cutting the RC.
> > >> > >> >
> > >> > >> > Thanks,
> > >> > >> > Gregor
> > >> > >> >
> > >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> > >> > >> wrote:
> > >> > >> > >
> > >> > >> > > Hi
> > >> > >> > >
> > >> > >> > > I think we should close down on the last bits and get milestone 4
> > >> > >> > > released and in the hands to the community.
> > >> > >> > >
> > >> > >> > > We had a number of significant improvements and features such as:
> > >> > >> > >
> > >> > >> > > 1) Endpoint DSL
> > >> > >> > > Type safe fluent builder for configuring endpoints in Java
> > >> > >> > >
> > >> > >> > > 2) Camel Main
> > >> > >> > > Standalone Camel for microservices
> > >> > >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap
> > >> Camel
> > >> > >> > >
> > >> > >> > > 3) camel-core-engine
> > >> > >> > > Tiny set of dependencies (only include absolutely what you need)
> > >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs
> > >> on
> > >> > >> classpath
> > >> > >> > >
> > >> > >> > > 4) components depend on camel-support
> > >> > >> > > Further reduced the dependency directly on camel-core for all
> > >> set of
> > >> > >> > > components. To ensure we use camel-api/camel-support for
> > >> components
> > >> > >> > > only.
> > >> > >> > >
> > >> > >> > > 5) lazy start producer
> > >> > >> > > You can configure in the endpoint that the producer should lazy
> > >> start
> > >> > >> > > (eg on 1st message) you can use this to allow Camel to startup
> > >> even if
> > >> > >> > > the producer would fail on startup - but now that failure is
> > >> deferred
> > >> > >> > > to 1st message which you can then use Camels route error handler
> > >> to
> > >> > >> > > deal with etc
> > >> > >> > >
> > >> > >> > > 6) SPI for Reactive Engine
> > >> > >> > > So we can plugin a different engine such as Camel Quarkus can
> > >> benefit
> > >> > >> > > from using its reactive engine.
> > >> > >> > >
> > >> > >> > > 7) DSL more extensive
> > >> > >> > > The reifiers and DSL model is more extensive/expandable. For
> > >> example a
> > >> > >> > > new yaml dsl flow is developed at Camel K that required some of
> > >> these
> > >> > >> > > changes.
> > >> > >> > >
> > >> > >> > > 8) Properties component / placeholder
> > >> > >> > > We can now easier extend this and also plugin to more 3rd
> > >> parties such
> > >> > >> > > as Eclipse MicroProfile Config (which is also needed by Camel
> > >> Quarkus)
> > >> > >> > >
> > >> > >> > > 9) Usual stuff
> > >> > >> > > Like bug fixes and whatnot.
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > I am currently working on getting the property component and
> > >> > >> > > placeholder refactored so it works better and can easier to
> > >> integrated
> > >> > >> > > with other configuration libraries. Also it would allow us to
> > >> > >> > > differentiate between read-only placeholders that can be loaded
> > >> at
> > >> > >> > > once, and others that are on-demand (eg to lookup in a database,
> > >> > >> > > hashicorp vault etc.)
> > >> > >> > >
> > >> > >> > > Also the CI build server is now 100% passing for the last couple
> > >> of
> > >> > >> days.
> > >> > >> > >
> > >> > >> > > So lets see if we can get the last bits done by end of tomorrow
> > >> or end
> > >> > >> > > of next week, and get a RC cut.
> > >> > >> > >
> > >> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
> > >> upgrade
> > >> > >> and use.
> > >> > >> > >
> > >> > >> > > Any thoughts?
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > --
> > >> > >> > > Claus Ibsen
> > >> > >> > > -----------------
> > >> > >> > > http://davsclaus.com @davsclaus
> > >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> --
> > >> > >> Claus Ibsen
> > >> > >> -----------------
> > >> > >> http://davsclaus.com @davsclaus
> > >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > >> > >>
> > >> > >
> > >>
> > >>
> > >>
> > >> --
> > >> Claus Ibsen
> > >> -----------------
> > >> http://davsclaus.com @davsclaus
> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > >>
> > >
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Thanks I got a word-wrap in the source code generate, will commit it
when it has regen the components
On Fri, Jul 5, 2019 at 2:31 PM Andrea Cosentino <an...@gmail.com> wrote:
>
> Fixed.
>
> Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <an...@gmail.com>
> ha scritto:
>
> > We can override the property
> >
> > https://checkstyle.sourceforge.io/config_sizes.html#FileLength
> >
> > We can put 10000
> >
> > Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <cl...@gmail.com>
> > ha scritto:
> >
> >> Hi
> >>
> >> Just a heads up that the checkstyle for endpoint-dsl will report some
> >> errors
> >> https://issues.apache.org/jira/browse/CAMEL-13728
> >>
> >> As this is generated we cannot keep the source files below 5000 lines etc.
> >> And also some javadoc lines are long, as we would need to word-wrap
> >> them ourselves
> >> to make this shorter.
> >>
> >> But I assume the RC can be cut anyway, just skip CS for this module or in
> >> total.
> >>
> >> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com>
> >> wrote:
> >> >
> >> > I've done with that documentation stuff. Gregor, when you are available,
> >> > let us know.
> >> >
> >> > Thanks
> >> >
> >> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> >> ancosen@gmail.com>
> >> > ha scritto:
> >> >
> >> > > I should finish a couple of things on the AWS components for
> >> documenting
> >> > > the region stuff. I should finish soon and send email
> >> > >
> >> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> >> claus.ibsen@gmail.com>
> >> > > ha scritto:
> >> > >
> >> > >> Hi
> >> > >>
> >> > >> I think the master branch is ready for a RC cut.
> >> > >>
> >> > >> Let us know if/when you get started Gregor
> >> > >>
> >> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> >> gregor@list.zurowski.org>
> >> > >> wrote:
> >> > >> >
> >> > >> > +1
> >> > >> >
> >> > >> > I'll be available for cutting the RC.
> >> > >> >
> >> > >> > Thanks,
> >> > >> > Gregor
> >> > >> >
> >> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> >> > >> wrote:
> >> > >> > >
> >> > >> > > Hi
> >> > >> > >
> >> > >> > > I think we should close down on the last bits and get milestone 4
> >> > >> > > released and in the hands to the community.
> >> > >> > >
> >> > >> > > We had a number of significant improvements and features such as:
> >> > >> > >
> >> > >> > > 1) Endpoint DSL
> >> > >> > > Type safe fluent builder for configuring endpoints in Java
> >> > >> > >
> >> > >> > > 2) Camel Main
> >> > >> > > Standalone Camel for microservices
> >> > >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap
> >> Camel
> >> > >> > >
> >> > >> > > 3) camel-core-engine
> >> > >> > > Tiny set of dependencies (only include absolutely what you need)
> >> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs
> >> on
> >> > >> classpath
> >> > >> > >
> >> > >> > > 4) components depend on camel-support
> >> > >> > > Further reduced the dependency directly on camel-core for all
> >> set of
> >> > >> > > components. To ensure we use camel-api/camel-support for
> >> components
> >> > >> > > only.
> >> > >> > >
> >> > >> > > 5) lazy start producer
> >> > >> > > You can configure in the endpoint that the producer should lazy
> >> start
> >> > >> > > (eg on 1st message) you can use this to allow Camel to startup
> >> even if
> >> > >> > > the producer would fail on startup - but now that failure is
> >> deferred
> >> > >> > > to 1st message which you can then use Camels route error handler
> >> to
> >> > >> > > deal with etc
> >> > >> > >
> >> > >> > > 6) SPI for Reactive Engine
> >> > >> > > So we can plugin a different engine such as Camel Quarkus can
> >> benefit
> >> > >> > > from using its reactive engine.
> >> > >> > >
> >> > >> > > 7) DSL more extensive
> >> > >> > > The reifiers and DSL model is more extensive/expandable. For
> >> example a
> >> > >> > > new yaml dsl flow is developed at Camel K that required some of
> >> these
> >> > >> > > changes.
> >> > >> > >
> >> > >> > > 8) Properties component / placeholder
> >> > >> > > We can now easier extend this and also plugin to more 3rd
> >> parties such
> >> > >> > > as Eclipse MicroProfile Config (which is also needed by Camel
> >> Quarkus)
> >> > >> > >
> >> > >> > > 9) Usual stuff
> >> > >> > > Like bug fixes and whatnot.
> >> > >> > >
> >> > >> > >
> >> > >> > > I am currently working on getting the property component and
> >> > >> > > placeholder refactored so it works better and can easier to
> >> integrated
> >> > >> > > with other configuration libraries. Also it would allow us to
> >> > >> > > differentiate between read-only placeholders that can be loaded
> >> at
> >> > >> > > once, and others that are on-demand (eg to lookup in a database,
> >> > >> > > hashicorp vault etc.)
> >> > >> > >
> >> > >> > > Also the CI build server is now 100% passing for the last couple
> >> of
> >> > >> days.
> >> > >> > >
> >> > >> > > So lets see if we can get the last bits done by end of tomorrow
> >> or end
> >> > >> > > of next week, and get a RC cut.
> >> > >> > >
> >> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
> >> upgrade
> >> > >> and use.
> >> > >> > >
> >> > >> > > Any thoughts?
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > --
> >> > >> > > Claus Ibsen
> >> > >> > > -----------------
> >> > >> > > http://davsclaus.com @davsclaus
> >> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> >> > >>
> >> > >>
> >> > >>
> >> > >> --
> >> > >> Claus Ibsen
> >> > >> -----------------
> >> > >> http://davsclaus.com @davsclaus
> >> > >> Camel in Action 2: https://www.manning.com/ibsen2
> >> > >>
> >> > >
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
Fixed.
Il giorno ven 5 lug 2019 alle ore 14:23 Andrea Cosentino <an...@gmail.com>
ha scritto:
> We can override the property
>
> https://checkstyle.sourceforge.io/config_sizes.html#FileLength
>
> We can put 10000
>
> Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <cl...@gmail.com>
> ha scritto:
>
>> Hi
>>
>> Just a heads up that the checkstyle for endpoint-dsl will report some
>> errors
>> https://issues.apache.org/jira/browse/CAMEL-13728
>>
>> As this is generated we cannot keep the source files below 5000 lines etc.
>> And also some javadoc lines are long, as we would need to word-wrap
>> them ourselves
>> to make this shorter.
>>
>> But I assume the RC can be cut anyway, just skip CS for this module or in
>> total.
>>
>> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com>
>> wrote:
>> >
>> > I've done with that documentation stuff. Gregor, when you are available,
>> > let us know.
>> >
>> > Thanks
>> >
>> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
>> ancosen@gmail.com>
>> > ha scritto:
>> >
>> > > I should finish a couple of things on the AWS components for
>> documenting
>> > > the region stuff. I should finish soon and send email
>> > >
>> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
>> claus.ibsen@gmail.com>
>> > > ha scritto:
>> > >
>> > >> Hi
>> > >>
>> > >> I think the master branch is ready for a RC cut.
>> > >>
>> > >> Let us know if/when you get started Gregor
>> > >>
>> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
>> gregor@list.zurowski.org>
>> > >> wrote:
>> > >> >
>> > >> > +1
>> > >> >
>> > >> > I'll be available for cutting the RC.
>> > >> >
>> > >> > Thanks,
>> > >> > Gregor
>> > >> >
>> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
>> > >> wrote:
>> > >> > >
>> > >> > > Hi
>> > >> > >
>> > >> > > I think we should close down on the last bits and get milestone 4
>> > >> > > released and in the hands to the community.
>> > >> > >
>> > >> > > We had a number of significant improvements and features such as:
>> > >> > >
>> > >> > > 1) Endpoint DSL
>> > >> > > Type safe fluent builder for configuring endpoints in Java
>> > >> > >
>> > >> > > 2) Camel Main
>> > >> > > Standalone Camel for microservices
>> > >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap
>> Camel
>> > >> > >
>> > >> > > 3) camel-core-engine
>> > >> > > Tiny set of dependencies (only include absolutely what you need)
>> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs
>> on
>> > >> classpath
>> > >> > >
>> > >> > > 4) components depend on camel-support
>> > >> > > Further reduced the dependency directly on camel-core for all
>> set of
>> > >> > > components. To ensure we use camel-api/camel-support for
>> components
>> > >> > > only.
>> > >> > >
>> > >> > > 5) lazy start producer
>> > >> > > You can configure in the endpoint that the producer should lazy
>> start
>> > >> > > (eg on 1st message) you can use this to allow Camel to startup
>> even if
>> > >> > > the producer would fail on startup - but now that failure is
>> deferred
>> > >> > > to 1st message which you can then use Camels route error handler
>> to
>> > >> > > deal with etc
>> > >> > >
>> > >> > > 6) SPI for Reactive Engine
>> > >> > > So we can plugin a different engine such as Camel Quarkus can
>> benefit
>> > >> > > from using its reactive engine.
>> > >> > >
>> > >> > > 7) DSL more extensive
>> > >> > > The reifiers and DSL model is more extensive/expandable. For
>> example a
>> > >> > > new yaml dsl flow is developed at Camel K that required some of
>> these
>> > >> > > changes.
>> > >> > >
>> > >> > > 8) Properties component / placeholder
>> > >> > > We can now easier extend this and also plugin to more 3rd
>> parties such
>> > >> > > as Eclipse MicroProfile Config (which is also needed by Camel
>> Quarkus)
>> > >> > >
>> > >> > > 9) Usual stuff
>> > >> > > Like bug fixes and whatnot.
>> > >> > >
>> > >> > >
>> > >> > > I am currently working on getting the property component and
>> > >> > > placeholder refactored so it works better and can easier to
>> integrated
>> > >> > > with other configuration libraries. Also it would allow us to
>> > >> > > differentiate between read-only placeholders that can be loaded
>> at
>> > >> > > once, and others that are on-demand (eg to lookup in a database,
>> > >> > > hashicorp vault etc.)
>> > >> > >
>> > >> > > Also the CI build server is now 100% passing for the last couple
>> of
>> > >> days.
>> > >> > >
>> > >> > > So lets see if we can get the last bits done by end of tomorrow
>> or end
>> > >> > > of next week, and get a RC cut.
>> > >> > >
>> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
>> upgrade
>> > >> and use.
>> > >> > >
>> > >> > > Any thoughts?
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > --
>> > >> > > Claus Ibsen
>> > >> > > -----------------
>> > >> > > http://davsclaus.com @davsclaus
>> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Claus Ibsen
>> > >> -----------------
>> > >> http://davsclaus.com @davsclaus
>> > >> Camel in Action 2: https://www.manning.com/ibsen2
>> > >>
>> > >
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
We can override the property
https://checkstyle.sourceforge.io/config_sizes.html#FileLength
We can put 10000
Il giorno ven 5 lug 2019 alle ore 14:20 Claus Ibsen <cl...@gmail.com>
ha scritto:
> Hi
>
> Just a heads up that the checkstyle for endpoint-dsl will report some
> errors
> https://issues.apache.org/jira/browse/CAMEL-13728
>
> As this is generated we cannot keep the source files below 5000 lines etc.
> And also some javadoc lines are long, as we would need to word-wrap
> them ourselves
> to make this shorter.
>
> But I assume the RC can be cut anyway, just skip CS for this module or in
> total.
>
> On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com> wrote:
> >
> > I've done with that documentation stuff. Gregor, when you are available,
> > let us know.
> >
> > Thanks
> >
> > Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <
> ancosen@gmail.com>
> > ha scritto:
> >
> > > I should finish a couple of things on the AWS components for
> documenting
> > > the region stuff. I should finish soon and send email
> > >
> > > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <
> claus.ibsen@gmail.com>
> > > ha scritto:
> > >
> > >> Hi
> > >>
> > >> I think the master branch is ready for a RC cut.
> > >>
> > >> Let us know if/when you get started Gregor
> > >>
> > >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <
> gregor@list.zurowski.org>
> > >> wrote:
> > >> >
> > >> > +1
> > >> >
> > >> > I'll be available for cutting the RC.
> > >> >
> > >> > Thanks,
> > >> > Gregor
> > >> >
> > >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> > >> wrote:
> > >> > >
> > >> > > Hi
> > >> > >
> > >> > > I think we should close down on the last bits and get milestone 4
> > >> > > released and in the hands to the community.
> > >> > >
> > >> > > We had a number of significant improvements and features such as:
> > >> > >
> > >> > > 1) Endpoint DSL
> > >> > > Type safe fluent builder for configuring endpoints in Java
> > >> > >
> > >> > > 2) Camel Main
> > >> > > Standalone Camel for microservices
> > >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> > >> > >
> > >> > > 3) camel-core-engine
> > >> > > Tiny set of dependencies (only include absolutely what you need)
> > >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > >> classpath
> > >> > >
> > >> > > 4) components depend on camel-support
> > >> > > Further reduced the dependency directly on camel-core for all set
> of
> > >> > > components. To ensure we use camel-api/camel-support for
> components
> > >> > > only.
> > >> > >
> > >> > > 5) lazy start producer
> > >> > > You can configure in the endpoint that the producer should lazy
> start
> > >> > > (eg on 1st message) you can use this to allow Camel to startup
> even if
> > >> > > the producer would fail on startup - but now that failure is
> deferred
> > >> > > to 1st message which you can then use Camels route error handler
> to
> > >> > > deal with etc
> > >> > >
> > >> > > 6) SPI for Reactive Engine
> > >> > > So we can plugin a different engine such as Camel Quarkus can
> benefit
> > >> > > from using its reactive engine.
> > >> > >
> > >> > > 7) DSL more extensive
> > >> > > The reifiers and DSL model is more extensive/expandable. For
> example a
> > >> > > new yaml dsl flow is developed at Camel K that required some of
> these
> > >> > > changes.
> > >> > >
> > >> > > 8) Properties component / placeholder
> > >> > > We can now easier extend this and also plugin to more 3rd parties
> such
> > >> > > as Eclipse MicroProfile Config (which is also needed by Camel
> Quarkus)
> > >> > >
> > >> > > 9) Usual stuff
> > >> > > Like bug fixes and whatnot.
> > >> > >
> > >> > >
> > >> > > I am currently working on getting the property component and
> > >> > > placeholder refactored so it works better and can easier to
> integrated
> > >> > > with other configuration libraries. Also it would allow us to
> > >> > > differentiate between read-only placeholders that can be loaded at
> > >> > > once, and others that are on-demand (eg to lookup in a database,
> > >> > > hashicorp vault etc.)
> > >> > >
> > >> > > Also the CI build server is now 100% passing for the last couple
> of
> > >> days.
> > >> > >
> > >> > > So lets see if we can get the last bits done by end of tomorrow
> or end
> > >> > > of next week, and get a RC cut.
> > >> > >
> > >> > > And we also need a M4 for both Camel K and Camel Quarkus to
> upgrade
> > >> and use.
> > >> > >
> > >> > > Any thoughts?
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Claus Ibsen
> > >> > > -----------------
> > >> > > http://davsclaus.com @davsclaus
> > >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >>
> > >>
> > >>
> > >> --
> > >> Claus Ibsen
> > >> -----------------
> > >> http://davsclaus.com @davsclaus
> > >> Camel in Action 2: https://www.manning.com/ibsen2
> > >>
> > >
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Just a heads up that the checkstyle for endpoint-dsl will report some errors
https://issues.apache.org/jira/browse/CAMEL-13728
As this is generated we cannot keep the source files below 5000 lines etc.
And also some javadoc lines are long, as we would need to word-wrap
them ourselves
to make this shorter.
But I assume the RC can be cut anyway, just skip CS for this module or in total.
On Fri, Jul 5, 2019 at 2:10 PM Andrea Cosentino <an...@gmail.com> wrote:
>
> I've done with that documentation stuff. Gregor, when you are available,
> let us know.
>
> Thanks
>
> Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <an...@gmail.com>
> ha scritto:
>
> > I should finish a couple of things on the AWS components for documenting
> > the region stuff. I should finish soon and send email
> >
> > Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <cl...@gmail.com>
> > ha scritto:
> >
> >> Hi
> >>
> >> I think the master branch is ready for a RC cut.
> >>
> >> Let us know if/when you get started Gregor
> >>
> >> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <gr...@list.zurowski.org>
> >> wrote:
> >> >
> >> > +1
> >> >
> >> > I'll be available for cutting the RC.
> >> >
> >> > Thanks,
> >> > Gregor
> >> >
> >> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> >> wrote:
> >> > >
> >> > > Hi
> >> > >
> >> > > I think we should close down on the last bits and get milestone 4
> >> > > released and in the hands to the community.
> >> > >
> >> > > We had a number of significant improvements and features such as:
> >> > >
> >> > > 1) Endpoint DSL
> >> > > Type safe fluent builder for configuring endpoints in Java
> >> > >
> >> > > 2) Camel Main
> >> > > Standalone Camel for microservices
> >> > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> >> > >
> >> > > 3) camel-core-engine
> >> > > Tiny set of dependencies (only include absolutely what you need)
> >> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> >> classpath
> >> > >
> >> > > 4) components depend on camel-support
> >> > > Further reduced the dependency directly on camel-core for all set of
> >> > > components. To ensure we use camel-api/camel-support for components
> >> > > only.
> >> > >
> >> > > 5) lazy start producer
> >> > > You can configure in the endpoint that the producer should lazy start
> >> > > (eg on 1st message) you can use this to allow Camel to startup even if
> >> > > the producer would fail on startup - but now that failure is deferred
> >> > > to 1st message which you can then use Camels route error handler to
> >> > > deal with etc
> >> > >
> >> > > 6) SPI for Reactive Engine
> >> > > So we can plugin a different engine such as Camel Quarkus can benefit
> >> > > from using its reactive engine.
> >> > >
> >> > > 7) DSL more extensive
> >> > > The reifiers and DSL model is more extensive/expandable. For example a
> >> > > new yaml dsl flow is developed at Camel K that required some of these
> >> > > changes.
> >> > >
> >> > > 8) Properties component / placeholder
> >> > > We can now easier extend this and also plugin to more 3rd parties such
> >> > > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> >> > >
> >> > > 9) Usual stuff
> >> > > Like bug fixes and whatnot.
> >> > >
> >> > >
> >> > > I am currently working on getting the property component and
> >> > > placeholder refactored so it works better and can easier to integrated
> >> > > with other configuration libraries. Also it would allow us to
> >> > > differentiate between read-only placeholders that can be loaded at
> >> > > once, and others that are on-demand (eg to lookup in a database,
> >> > > hashicorp vault etc.)
> >> > >
> >> > > Also the CI build server is now 100% passing for the last couple of
> >> days.
> >> > >
> >> > > So lets see if we can get the last bits done by end of tomorrow or end
> >> > > of next week, and get a RC cut.
> >> > >
> >> > > And we also need a M4 for both Camel K and Camel Quarkus to upgrade
> >> and use.
> >> > >
> >> > > Any thoughts?
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Claus Ibsen
> >> > > -----------------
> >> > > http://davsclaus.com @davsclaus
> >> > > Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
I've done with that documentation stuff. Gregor, when you are available,
let us know.
Thanks
Il giorno ven 5 lug 2019 alle ore 12:12 Andrea Cosentino <an...@gmail.com>
ha scritto:
> I should finish a couple of things on the AWS components for documenting
> the region stuff. I should finish soon and send email
>
> Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <cl...@gmail.com>
> ha scritto:
>
>> Hi
>>
>> I think the master branch is ready for a RC cut.
>>
>> Let us know if/when you get started Gregor
>>
>> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <gr...@list.zurowski.org>
>> wrote:
>> >
>> > +1
>> >
>> > I'll be available for cutting the RC.
>> >
>> > Thanks,
>> > Gregor
>> >
>> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
>> wrote:
>> > >
>> > > Hi
>> > >
>> > > I think we should close down on the last bits and get milestone 4
>> > > released and in the hands to the community.
>> > >
>> > > We had a number of significant improvements and features such as:
>> > >
>> > > 1) Endpoint DSL
>> > > Type safe fluent builder for configuring endpoints in Java
>> > >
>> > > 2) Camel Main
>> > > Standalone Camel for microservices
>> > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>> > >
>> > > 3) camel-core-engine
>> > > Tiny set of dependencies (only include absolutely what you need)
>> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
>> classpath
>> > >
>> > > 4) components depend on camel-support
>> > > Further reduced the dependency directly on camel-core for all set of
>> > > components. To ensure we use camel-api/camel-support for components
>> > > only.
>> > >
>> > > 5) lazy start producer
>> > > You can configure in the endpoint that the producer should lazy start
>> > > (eg on 1st message) you can use this to allow Camel to startup even if
>> > > the producer would fail on startup - but now that failure is deferred
>> > > to 1st message which you can then use Camels route error handler to
>> > > deal with etc
>> > >
>> > > 6) SPI for Reactive Engine
>> > > So we can plugin a different engine such as Camel Quarkus can benefit
>> > > from using its reactive engine.
>> > >
>> > > 7) DSL more extensive
>> > > The reifiers and DSL model is more extensive/expandable. For example a
>> > > new yaml dsl flow is developed at Camel K that required some of these
>> > > changes.
>> > >
>> > > 8) Properties component / placeholder
>> > > We can now easier extend this and also plugin to more 3rd parties such
>> > > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>> > >
>> > > 9) Usual stuff
>> > > Like bug fixes and whatnot.
>> > >
>> > >
>> > > I am currently working on getting the property component and
>> > > placeholder refactored so it works better and can easier to integrated
>> > > with other configuration libraries. Also it would allow us to
>> > > differentiate between read-only placeholders that can be loaded at
>> > > once, and others that are on-demand (eg to lookup in a database,
>> > > hashicorp vault etc.)
>> > >
>> > > Also the CI build server is now 100% passing for the last couple of
>> days.
>> > >
>> > > So lets see if we can get the last bits done by end of tomorrow or end
>> > > of next week, and get a RC cut.
>> > >
>> > > And we also need a M4 for both Camel K and Camel Quarkus to upgrade
>> and use.
>> > >
>> > > Any thoughts?
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > Claus Ibsen
>> > > -----------------
>> > > http://davsclaus.com @davsclaus
>> > > Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
I should finish a couple of things on the AWS components for documenting
the region stuff. I should finish soon and send email
Il giorno ven 5 lug 2019 alle ore 12:06 Claus Ibsen <cl...@gmail.com>
ha scritto:
> Hi
>
> I think the master branch is ready for a RC cut.
>
> Let us know if/when you get started Gregor
>
> On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <gr...@list.zurowski.org>
> wrote:
> >
> > +1
> >
> > I'll be available for cutting the RC.
> >
> > Thanks,
> > Gregor
> >
> > On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com>
> wrote:
> > >
> > > Hi
> > >
> > > I think we should close down on the last bits and get milestone 4
> > > released and in the hands to the community.
> > >
> > > We had a number of significant improvements and features such as:
> > >
> > > 1) Endpoint DSL
> > > Type safe fluent builder for configuring endpoints in Java
> > >
> > > 2) Camel Main
> > > Standalone Camel for microservices
> > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> > >
> > > 3) camel-core-engine
> > > Tiny set of dependencies (only include absolutely what you need)
> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> classpath
> > >
> > > 4) components depend on camel-support
> > > Further reduced the dependency directly on camel-core for all set of
> > > components. To ensure we use camel-api/camel-support for components
> > > only.
> > >
> > > 5) lazy start producer
> > > You can configure in the endpoint that the producer should lazy start
> > > (eg on 1st message) you can use this to allow Camel to startup even if
> > > the producer would fail on startup - but now that failure is deferred
> > > to 1st message which you can then use Camels route error handler to
> > > deal with etc
> > >
> > > 6) SPI for Reactive Engine
> > > So we can plugin a different engine such as Camel Quarkus can benefit
> > > from using its reactive engine.
> > >
> > > 7) DSL more extensive
> > > The reifiers and DSL model is more extensive/expandable. For example a
> > > new yaml dsl flow is developed at Camel K that required some of these
> > > changes.
> > >
> > > 8) Properties component / placeholder
> > > We can now easier extend this and also plugin to more 3rd parties such
> > > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> > >
> > > 9) Usual stuff
> > > Like bug fixes and whatnot.
> > >
> > >
> > > I am currently working on getting the property component and
> > > placeholder refactored so it works better and can easier to integrated
> > > with other configuration libraries. Also it would allow us to
> > > differentiate between read-only placeholders that can be loaded at
> > > once, and others that are on-demand (eg to lookup in a database,
> > > hashicorp vault etc.)
> > >
> > > Also the CI build server is now 100% passing for the last couple of
> days.
> > >
> > > So lets see if we can get the last bits done by end of tomorrow or end
> > > of next week, and get a RC cut.
> > >
> > > And we also need a M4 for both Camel K and Camel Quarkus to upgrade
> and use.
> > >
> > > Any thoughts?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I think the master branch is ready for a RC cut.
Let us know if/when you get started Gregor
On Thu, Jul 4, 2019 at 4:02 PM Gregor Zurowski <gr...@list.zurowski.org> wrote:
>
> +1
>
> I'll be available for cutting the RC.
>
> Thanks,
> Gregor
>
> On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > I think we should close down on the last bits and get milestone 4
> > released and in the hands to the community.
> >
> > We had a number of significant improvements and features such as:
> >
> > 1) Endpoint DSL
> > Type safe fluent builder for configuring endpoints in Java
> >
> > 2) Camel Main
> > Standalone Camel for microservices
> > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> >
> > 3) camel-core-engine
> > Tiny set of dependencies (only include absolutely what you need)
> > Needed by Camel K and Camel Quarkus to have smaller set of JARs on classpath
> >
> > 4) components depend on camel-support
> > Further reduced the dependency directly on camel-core for all set of
> > components. To ensure we use camel-api/camel-support for components
> > only.
> >
> > 5) lazy start producer
> > You can configure in the endpoint that the producer should lazy start
> > (eg on 1st message) you can use this to allow Camel to startup even if
> > the producer would fail on startup - but now that failure is deferred
> > to 1st message which you can then use Camels route error handler to
> > deal with etc
> >
> > 6) SPI for Reactive Engine
> > So we can plugin a different engine such as Camel Quarkus can benefit
> > from using its reactive engine.
> >
> > 7) DSL more extensive
> > The reifiers and DSL model is more extensive/expandable. For example a
> > new yaml dsl flow is developed at Camel K that required some of these
> > changes.
> >
> > 8) Properties component / placeholder
> > We can now easier extend this and also plugin to more 3rd parties such
> > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> >
> > 9) Usual stuff
> > Like bug fixes and whatnot.
> >
> >
> > I am currently working on getting the property component and
> > placeholder refactored so it works better and can easier to integrated
> > with other configuration libraries. Also it would allow us to
> > differentiate between read-only placeholders that can be loaded at
> > once, and others that are on-demand (eg to lookup in a database,
> > hashicorp vault etc.)
> >
> > Also the CI build server is now 100% passing for the last couple of days.
> >
> > So lets see if we can get the last bits done by end of tomorrow or end
> > of next week, and get a RC cut.
> >
> > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and use.
> >
> > Any thoughts?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
+1
I'll be available for cutting the RC.
Thanks,
Gregor
On Thu, Jul 4, 2019 at 6:48 AM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> I think we should close down on the last bits and get milestone 4
> released and in the hands to the community.
>
> We had a number of significant improvements and features such as:
>
> 1) Endpoint DSL
> Type safe fluent builder for configuring endpoints in Java
>
> 2) Camel Main
> Standalone Camel for microservices
> Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>
> 3) camel-core-engine
> Tiny set of dependencies (only include absolutely what you need)
> Needed by Camel K and Camel Quarkus to have smaller set of JARs on classpath
>
> 4) components depend on camel-support
> Further reduced the dependency directly on camel-core for all set of
> components. To ensure we use camel-api/camel-support for components
> only.
>
> 5) lazy start producer
> You can configure in the endpoint that the producer should lazy start
> (eg on 1st message) you can use this to allow Camel to startup even if
> the producer would fail on startup - but now that failure is deferred
> to 1st message which you can then use Camels route error handler to
> deal with etc
>
> 6) SPI for Reactive Engine
> So we can plugin a different engine such as Camel Quarkus can benefit
> from using its reactive engine.
>
> 7) DSL more extensive
> The reifiers and DSL model is more extensive/expandable. For example a
> new yaml dsl flow is developed at Camel K that required some of these
> changes.
>
> 8) Properties component / placeholder
> We can now easier extend this and also plugin to more 3rd parties such
> as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>
> 9) Usual stuff
> Like bug fixes and whatnot.
>
>
> I am currently working on getting the property component and
> placeholder refactored so it works better and can easier to integrated
> with other configuration libraries. Also it would allow us to
> differentiate between read-only placeholders that can be loaded at
> once, and others that are on-demand (eg to lookup in a database,
> hashicorp vault etc.)
>
> Also the CI build server is now 100% passing for the last couple of days.
>
> So lets see if we can get the last bits done by end of tomorrow or end
> of next week, and get a RC cut.
>
> And we also need a M4 for both Camel K and Camel Quarkus to upgrade and use.
>
> Any thoughts?
>
>
>
>
>
>
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
For the moment, I reverted it.
Il giorno gio 4 lug 2019 alle ore 10:21 Claus Ibsen <cl...@gmail.com>
ha scritto:
> Hi
>
> Well spotted, yeah the spring-boot-dm BOM should also be generated
> correctly.
> It looks as if the JARs from camel-core are removed.
>
> The karaf commands is ofcourse not needed and can be removed as it was
> in the PR.
>
>
> On Thu, Jul 4, 2019 at 9:51 AM Andrea Cosentino <an...@gmail.com> wrote:
> >
> > I think we have to review this
> >
> https://github.com/apache/camel/commit/ffbe4efdc9e065b076a3952631facae46a1e25f3
> >
> > Rebuilding the whole project generate a different spring-boot-dm
> >
> > https://gist.github.com/oscerd/3eebfd1cec22af66f1d34cb44d70fedd
> >
> > With this stuff in, all the Spring Boot integration tests fail
> >
> > Il giorno gio 4 lug 2019 alle ore 09:47 Guillaume Nodet <
> gnodet@apache.org>
> > ha scritto:
> >
> > > +1 for a M4
> > >
> > > Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a
> écrit
> > > :
> > >
> > > > Hi
> > > >
> > > > I think we should close down on the last bits and get milestone 4
> > > > released and in the hands to the community.
> > > >
> > > > We had a number of significant improvements and features such as:
> > > >
> > > > 1) Endpoint DSL
> > > > Type safe fluent builder for configuring endpoints in Java
> > > >
> > > > 2) Camel Main
> > > > Standalone Camel for microservices
> > > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> > > >
> > > > 3) camel-core-engine
> > > > Tiny set of dependencies (only include absolutely what you need)
> > > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > > > classpath
> > > >
> > > > 4) components depend on camel-support
> > > > Further reduced the dependency directly on camel-core for all set of
> > > > components. To ensure we use camel-api/camel-support for components
> > > > only.
> > > >
> > > > 5) lazy start producer
> > > > You can configure in the endpoint that the producer should lazy start
> > > > (eg on 1st message) you can use this to allow Camel to startup even
> if
> > > > the producer would fail on startup - but now that failure is deferred
> > > > to 1st message which you can then use Camels route error handler to
> > > > deal with etc
> > > >
> > > > 6) SPI for Reactive Engine
> > > > So we can plugin a different engine such as Camel Quarkus can benefit
> > > > from using its reactive engine.
> > > >
> > > > 7) DSL more extensive
> > > > The reifiers and DSL model is more extensive/expandable. For example
> a
> > > > new yaml dsl flow is developed at Camel K that required some of these
> > > > changes.
> > > >
> > > > 8) Properties component / placeholder
> > > > We can now easier extend this and also plugin to more 3rd parties
> such
> > > > as Eclipse MicroProfile Config (which is also needed by Camel
> Quarkus)
> > > >
> > > > 9) Usual stuff
> > > > Like bug fixes and whatnot.
> > > >
> > > >
> > > > I am currently working on getting the property component and
> > > > placeholder refactored so it works better and can easier to
> integrated
> > > > with other configuration libraries. Also it would allow us to
> > > > differentiate between read-only placeholders that can be loaded at
> > > > once, and others that are on-demand (eg to lookup in a database,
> > > > hashicorp vault etc.)
> > > >
> > > > Also the CI build server is now 100% passing for the last couple of
> days.
> > > >
> > > > So lets see if we can get the last bits done by end of tomorrow or
> end
> > > > of next week, and get a RC cut.
> > > >
> > > > And we also need a M4 for both Camel K and Camel Quarkus to upgrade
> and
> > > > use.
> > > >
> > > > Any thoughts?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -----------------
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> > >
> > > --
> > > ------------------------
> > > Guillaume Nodet
> > >
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Well spotted, yeah the spring-boot-dm BOM should also be generated correctly.
It looks as if the JARs from camel-core are removed.
The karaf commands is ofcourse not needed and can be removed as it was
in the PR.
On Thu, Jul 4, 2019 at 9:51 AM Andrea Cosentino <an...@gmail.com> wrote:
>
> I think we have to review this
> https://github.com/apache/camel/commit/ffbe4efdc9e065b076a3952631facae46a1e25f3
>
> Rebuilding the whole project generate a different spring-boot-dm
>
> https://gist.github.com/oscerd/3eebfd1cec22af66f1d34cb44d70fedd
>
> With this stuff in, all the Spring Boot integration tests fail
>
> Il giorno gio 4 lug 2019 alle ore 09:47 Guillaume Nodet <gn...@apache.org>
> ha scritto:
>
> > +1 for a M4
> >
> > Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a écrit
> > :
> >
> > > Hi
> > >
> > > I think we should close down on the last bits and get milestone 4
> > > released and in the hands to the community.
> > >
> > > We had a number of significant improvements and features such as:
> > >
> > > 1) Endpoint DSL
> > > Type safe fluent builder for configuring endpoints in Java
> > >
> > > 2) Camel Main
> > > Standalone Camel for microservices
> > > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> > >
> > > 3) camel-core-engine
> > > Tiny set of dependencies (only include absolutely what you need)
> > > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > > classpath
> > >
> > > 4) components depend on camel-support
> > > Further reduced the dependency directly on camel-core for all set of
> > > components. To ensure we use camel-api/camel-support for components
> > > only.
> > >
> > > 5) lazy start producer
> > > You can configure in the endpoint that the producer should lazy start
> > > (eg on 1st message) you can use this to allow Camel to startup even if
> > > the producer would fail on startup - but now that failure is deferred
> > > to 1st message which you can then use Camels route error handler to
> > > deal with etc
> > >
> > > 6) SPI for Reactive Engine
> > > So we can plugin a different engine such as Camel Quarkus can benefit
> > > from using its reactive engine.
> > >
> > > 7) DSL more extensive
> > > The reifiers and DSL model is more extensive/expandable. For example a
> > > new yaml dsl flow is developed at Camel K that required some of these
> > > changes.
> > >
> > > 8) Properties component / placeholder
> > > We can now easier extend this and also plugin to more 3rd parties such
> > > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> > >
> > > 9) Usual stuff
> > > Like bug fixes and whatnot.
> > >
> > >
> > > I am currently working on getting the property component and
> > > placeholder refactored so it works better and can easier to integrated
> > > with other configuration libraries. Also it would allow us to
> > > differentiate between read-only placeholders that can be loaded at
> > > once, and others that are on-demand (eg to lookup in a database,
> > > hashicorp vault etc.)
> > >
> > > Also the CI build server is now 100% passing for the last couple of days.
> > >
> > > So lets see if we can get the last bits done by end of tomorrow or end
> > > of next week, and get a RC cut.
> > >
> > > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> > > use.
> > >
> > > Any thoughts?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > ------------------------
> > Guillaume Nodet
> >
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
I think it must be reverted
Il giorno gio 4 lug 2019 alle ore 09:50 Andrea Cosentino <an...@gmail.com>
ha scritto:
> I think we have to review this
> https://github.com/apache/camel/commit/ffbe4efdc9e065b076a3952631facae46a1e25f3
>
> Rebuilding the whole project generate a different spring-boot-dm
>
> https://gist.github.com/oscerd/3eebfd1cec22af66f1d34cb44d70fedd
>
> With this stuff in, all the Spring Boot integration tests fail
>
> Il giorno gio 4 lug 2019 alle ore 09:47 Guillaume Nodet <gn...@apache.org>
> ha scritto:
>
>> +1 for a M4
>>
>> Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a
>> écrit :
>>
>> > Hi
>> >
>> > I think we should close down on the last bits and get milestone 4
>> > released and in the hands to the community.
>> >
>> > We had a number of significant improvements and features such as:
>> >
>> > 1) Endpoint DSL
>> > Type safe fluent builder for configuring endpoints in Java
>> >
>> > 2) Camel Main
>> > Standalone Camel for microservices
>> > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>> >
>> > 3) camel-core-engine
>> > Tiny set of dependencies (only include absolutely what you need)
>> > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
>> > classpath
>> >
>> > 4) components depend on camel-support
>> > Further reduced the dependency directly on camel-core for all set of
>> > components. To ensure we use camel-api/camel-support for components
>> > only.
>> >
>> > 5) lazy start producer
>> > You can configure in the endpoint that the producer should lazy start
>> > (eg on 1st message) you can use this to allow Camel to startup even if
>> > the producer would fail on startup - but now that failure is deferred
>> > to 1st message which you can then use Camels route error handler to
>> > deal with etc
>> >
>> > 6) SPI for Reactive Engine
>> > So we can plugin a different engine such as Camel Quarkus can benefit
>> > from using its reactive engine.
>> >
>> > 7) DSL more extensive
>> > The reifiers and DSL model is more extensive/expandable. For example a
>> > new yaml dsl flow is developed at Camel K that required some of these
>> > changes.
>> >
>> > 8) Properties component / placeholder
>> > We can now easier extend this and also plugin to more 3rd parties such
>> > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>> >
>> > 9) Usual stuff
>> > Like bug fixes and whatnot.
>> >
>> >
>> > I am currently working on getting the property component and
>> > placeholder refactored so it works better and can easier to integrated
>> > with other configuration libraries. Also it would allow us to
>> > differentiate between read-only placeholders that can be loaded at
>> > once, and others that are on-demand (eg to lookup in a database,
>> > hashicorp vault etc.)
>> >
>> > Also the CI build server is now 100% passing for the last couple of
>> days.
>> >
>> > So lets see if we can get the last bits done by end of tomorrow or end
>> > of next week, and get a RC cut.
>> >
>> > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
>> > use.
>> >
>> > Any thoughts?
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2: https://www.manning.com/ibsen2
>> >
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>>
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Andrea Cosentino <an...@gmail.com>.
I think we have to review this
https://github.com/apache/camel/commit/ffbe4efdc9e065b076a3952631facae46a1e25f3
Rebuilding the whole project generate a different spring-boot-dm
https://gist.github.com/oscerd/3eebfd1cec22af66f1d34cb44d70fedd
With this stuff in, all the Spring Boot integration tests fail
Il giorno gio 4 lug 2019 alle ore 09:47 Guillaume Nodet <gn...@apache.org>
ha scritto:
> +1 for a M4
>
> Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a écrit
> :
>
> > Hi
> >
> > I think we should close down on the last bits and get milestone 4
> > released and in the hands to the community.
> >
> > We had a number of significant improvements and features such as:
> >
> > 1) Endpoint DSL
> > Type safe fluent builder for configuring endpoints in Java
> >
> > 2) Camel Main
> > Standalone Camel for microservices
> > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> >
> > 3) camel-core-engine
> > Tiny set of dependencies (only include absolutely what you need)
> > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > classpath
> >
> > 4) components depend on camel-support
> > Further reduced the dependency directly on camel-core for all set of
> > components. To ensure we use camel-api/camel-support for components
> > only.
> >
> > 5) lazy start producer
> > You can configure in the endpoint that the producer should lazy start
> > (eg on 1st message) you can use this to allow Camel to startup even if
> > the producer would fail on startup - but now that failure is deferred
> > to 1st message which you can then use Camels route error handler to
> > deal with etc
> >
> > 6) SPI for Reactive Engine
> > So we can plugin a different engine such as Camel Quarkus can benefit
> > from using its reactive engine.
> >
> > 7) DSL more extensive
> > The reifiers and DSL model is more extensive/expandable. For example a
> > new yaml dsl flow is developed at Camel K that required some of these
> > changes.
> >
> > 8) Properties component / placeholder
> > We can now easier extend this and also plugin to more 3rd parties such
> > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> >
> > 9) Usual stuff
> > Like bug fixes and whatnot.
> >
> >
> > I am currently working on getting the property component and
> > placeholder refactored so it works better and can easier to integrated
> > with other configuration libraries. Also it would allow us to
> > differentiate between read-only placeholders that can be loaded at
> > once, and others that are on-demand (eg to lookup in a database,
> > hashicorp vault etc.)
> >
> > Also the CI build server is now 100% passing for the last couple of days.
> >
> > So lets see if we can get the last bits done by end of tomorrow or end
> > of next week, and get a RC cut.
> >
> > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> > use.
> >
> > Any thoughts?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> ------------------------
> Guillaume Nodet
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Luca Burgazzoli <lb...@gmail.com>.
+1
---
Luca Burgazzoli
On Thu, Jul 4, 2019 at 9:47 AM Guillaume Nodet <gn...@apache.org> wrote:
> +1 for a M4
>
> Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a écrit
> :
>
> > Hi
> >
> > I think we should close down on the last bits and get milestone 4
> > released and in the hands to the community.
> >
> > We had a number of significant improvements and features such as:
> >
> > 1) Endpoint DSL
> > Type safe fluent builder for configuring endpoints in Java
> >
> > 2) Camel Main
> > Standalone Camel for microservices
> > Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
> >
> > 3) camel-core-engine
> > Tiny set of dependencies (only include absolutely what you need)
> > Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> > classpath
> >
> > 4) components depend on camel-support
> > Further reduced the dependency directly on camel-core for all set of
> > components. To ensure we use camel-api/camel-support for components
> > only.
> >
> > 5) lazy start producer
> > You can configure in the endpoint that the producer should lazy start
> > (eg on 1st message) you can use this to allow Camel to startup even if
> > the producer would fail on startup - but now that failure is deferred
> > to 1st message which you can then use Camels route error handler to
> > deal with etc
> >
> > 6) SPI for Reactive Engine
> > So we can plugin a different engine such as Camel Quarkus can benefit
> > from using its reactive engine.
> >
> > 7) DSL more extensive
> > The reifiers and DSL model is more extensive/expandable. For example a
> > new yaml dsl flow is developed at Camel K that required some of these
> > changes.
> >
> > 8) Properties component / placeholder
> > We can now easier extend this and also plugin to more 3rd parties such
> > as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
> >
> > 9) Usual stuff
> > Like bug fixes and whatnot.
> >
> >
> > I am currently working on getting the property component and
> > placeholder refactored so it works better and can easier to integrated
> > with other configuration libraries. Also it would allow us to
> > differentiate between read-only placeholders that can be loaded at
> > once, and others that are on-demand (eg to lookup in a database,
> > hashicorp vault etc.)
> >
> > Also the CI build server is now 100% passing for the last couple of days.
> >
> > So lets see if we can get the last bits done by end of tomorrow or end
> > of next week, and get a RC cut.
> >
> > And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> > use.
> >
> > Any thoughts?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> ------------------------
> Guillaume Nodet
>
Re: Apache Camel 3 milestone 4 close down and release soon
Posted by Guillaume Nodet <gn...@apache.org>.
+1 for a M4
Le jeu. 4 juil. 2019 à 06:48, Claus Ibsen <cl...@gmail.com> a écrit :
> Hi
>
> I think we should close down on the last bits and get milestone 4
> released and in the hands to the community.
>
> We had a number of significant improvements and features such as:
>
> 1) Endpoint DSL
> Type safe fluent builder for configuring endpoints in Java
>
> 2) Camel Main
> Standalone Camel for microservices
> Needed for Camel K and Camel Quarkus as the way to bootstrap Camel
>
> 3) camel-core-engine
> Tiny set of dependencies (only include absolutely what you need)
> Needed by Camel K and Camel Quarkus to have smaller set of JARs on
> classpath
>
> 4) components depend on camel-support
> Further reduced the dependency directly on camel-core for all set of
> components. To ensure we use camel-api/camel-support for components
> only.
>
> 5) lazy start producer
> You can configure in the endpoint that the producer should lazy start
> (eg on 1st message) you can use this to allow Camel to startup even if
> the producer would fail on startup - but now that failure is deferred
> to 1st message which you can then use Camels route error handler to
> deal with etc
>
> 6) SPI for Reactive Engine
> So we can plugin a different engine such as Camel Quarkus can benefit
> from using its reactive engine.
>
> 7) DSL more extensive
> The reifiers and DSL model is more extensive/expandable. For example a
> new yaml dsl flow is developed at Camel K that required some of these
> changes.
>
> 8) Properties component / placeholder
> We can now easier extend this and also plugin to more 3rd parties such
> as Eclipse MicroProfile Config (which is also needed by Camel Quarkus)
>
> 9) Usual stuff
> Like bug fixes and whatnot.
>
>
> I am currently working on getting the property component and
> placeholder refactored so it works better and can easier to integrated
> with other configuration libraries. Also it would allow us to
> differentiate between read-only placeholders that can be loaded at
> once, and others that are on-demand (eg to lookup in a database,
> hashicorp vault etc.)
>
> Also the CI build server is now 100% passing for the last couple of days.
>
> So lets see if we can get the last bits done by end of tomorrow or end
> of next week, and get a RC cut.
>
> And we also need a M4 for both Camel K and Camel Quarkus to upgrade and
> use.
>
> Any thoughts?
>
>
>
>
>
>
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
------------------------
Guillaume Nodet