Le lun. 27 janv. 2020 à 11:19, Claus Ibsen <claus.ib...@gmail.com> a écrit :
> 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. > Right, that's still on my todo list. If anyone wants to look at it while I'm working on #2, please be my guest. > > 2) > Generate source code configurer for data formats and languages > I'm on it, though a bit side tracked. I'm currently unifying the internal meta-model representation. I've pushed most of the work, but I still need to work on the catalog to use a pojos instead of the "rows" based schema. Along with the dataformats and languages reifications, we may revisit the core definition's reification (see CAMEL-14445). > > 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) > If anyone wants to look it at, he'd be welcomed. Basically, we'd need to make ModelHelper.loadRoutesDefinition / loadRestsDefinition pluggable. Either using a ad-hoc system or a discoverable service using META-INF/services > > There are other things of course, but these are the bigger high level > things I could remember. > One thing I'd like to do too is to continue cleaning the build / internal tooling by migrating the apt processors into maven plugins and to move all generated code in the source tree, but this can be delayed if needed. > 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 > -- ------------------------ Guillaume Nodet
