On Mon, Feb 10, 2020 at 11:09 AM Omar Al-Safi <o...@oalsafi.com> wrote: > > I can help on moving the camel-examples, of course if no one is working on > it currently
Yeah sure that would be good. The git repo has been setup and there is a basic readme file. I think the examples can be moved under examples so they are not in the root folder to clutter up. > > On Mon, Feb 10, 2020 at 10:19 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > Hi > > > > We have had great progress on Camel 3.1 and are missing a few things left > > > > 1) > > Finish the separation of camel-spring-boot (there are some tools that > > update docs and generate component list) that needs to be completed. > > > > I will work on making something similar to what we do with camel-quarkus. > > > > 2) > > Generate configurer for languages. gnodet did you do this? > > > > 3) > > Move examples to camel-examples > > > > 4) > > Avoid property placeholder resolution inside the definitions and > > generation of model configurers. > > > > 5) > > 3rd party components. Allow to generate endpoint and component DSL > > > > 6) > > A bug reported about problems with camel-blueprint > > > > 7) > > AWS2 components > > > > 8) > > And then the usual smaller things reported by the community and so on. > > > > > > > > On Mon, Jan 27, 2020 at 11:18 AM Claus Ibsen <claus.ib...@gmail.com> > > wrote: > > > > > > Hi > > > > > > I just wanted to start the process of getting closer to Camel 3.1 > > release. > > > Despite 3.0 was released only a while back, then we have made great > > > progress on 3.1 that is important to get in the hands of the Camel > > > users. And for Camel users that migrate to 3.x can then skip 3.0 and > > > go straight to 3.1. > > > > > > I am working on some further optimizations in the core for 3.1, and I > > > hope to find time to share more details in a blog. > > > > > > However to get the other work (high level) done and ready for 3.1, > > > then lets discuss them here on the @dev mailing list. > > > > > > On top of my head we have to do > > > > > > 1) > > > Finish the separation of camel-spring-boot (there are some tools that > > > update docs and generate component list) that needs to be completed. > > > > > > 2) > > > Generate source code configurer for data formats and languages > > > > > > 3) > > > The component configuration fluent builder (would be nice) > > > > > > 4) > > > More camel AWS SDK2 components > > > > > > 5) > > > Camel Main to plugin the new lightweight XML route parser/loader (for > > > example auto discover on classpath the JAR and use it instead of JAXB) > > > > > > There are other things of course, but these are the bigger high level > > > things I could remember. > > > > > > The usual work with new components, examples, other improvements is of > > > course also ongoing. > > > > > > Lets see if we can get this done and release Camel 3.1 in February. > > > > > > > > > > > > > > > -- > > > 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
