(Please reply-all, as I'm not currently subscribed to the list) I'm familiar with `polyglot-maven` as the prior art here, but I'm concerned about extensible syntax as a first-class feature.
I know I'm really late to this, but I think that Maven POM syntax should _not_ be extensible; instead, there should be first-class support for a single, modern build POM syntax. This would be a much better move for the overall ecosystem: tech writers, IDEs, LSPs, `mvnup`, and third-party tooling (OpenRewrite, Dependabot, AI coding agents, starship, etc) would all know what they need to support, much like when Gradle added support for the Kotlin DSL. Having too many syntax options, whether first-party or third-party, is a recipe for confusion and fragmentation, as I've repeatedly seen with Log4j2 configuration. Third-party syntaxes in particular are likely to suffer from poor design choices and quality issues that could be avoided through the additional scrutiny that an official successor syntax would undergo. Having an SPI as part of 4.0 doesn't foreclose the possibility of an official successor syntax, but I would hope that that's the ultimate end goal here. On Sun, Dec 28, 2025 at 4:59 AM Ryan Schmitt <[email protected]> wrote: > I'm looking for more information on this Maven 4 feature, which I > understand to be an official SPI for POM file parsers, to allow the use of > formats other than XML. I have some thoughts on this feature, but I'd first > like to read any prior design discussions; I wasn't immediately able to > find any relevant threads in the archives for this list. >
