Hello, Not exactly sure what work you mean and I fully agree that using a core model should still be the API for plugins and extensions to work with, however specifically the consumer POM integrates with so many external ecosystems, I would expect it to be defined in terms of XML Schema with explicite semantic (and the inherent compatibility with exiting POMs).
Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Matthieu BROUILLARD <matth...@brouillard.fr> Gesendet: Thursday, December 31, 2020 3:19:09 PM An: dev@maven.apache.org <dev@maven.apache.org> Betreff: maven 4.0.0 new XML stuff Hello all, regarding the active work occurring for maven 4.0.0 I noticed the introduction of a lot of new stuff around SAX parsing & filtering. I am wondering if that means that it was decided that the input format of maven projects will be XML forever meaning probably, among others, the end of polyglot extensions. Could you explain such a move (or point to rationals/documents) and why you did not leverage working on the in memory object model allowing extensions/plugins to contribute/hook in the chain of building the BuildPOM & ConsumePOM? In the past I really thought that this move to 'Build vs Consumer' POM would make clear separations between the input format of descriptors and the core system but I perhaps misunderstood things. Also, are there plans regarding the future of core extensions? With core extensions it was possible to hook into the POM model loading and do transformations to do dynamic changes but by working on the XML directly I see a shift (if not red stop) in this contribution/delegation mechanism. Thanks for your time & answers. Matthieu Brouillard
