Working on some minor improvement for camel-main required for camel-k, should be ready by this week
--- Luca Burgazzoli On Mon, Jan 27, 2020 at 2:35 PM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 > > I still have my Karaf improvements local branch for Camel 3.x. But not a > blocker for 3.1 release. > > Regards > JB > > On 27/01/2020 11:18, Claus Ibsen 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. > > > > > > > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
