rschmitt commented on issue #9083: URL: https://github.com/apache/maven/issues/9083#issuecomment-3694174399
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 POM syntax. This would be a much better move for the overall ecosystem: tech writers, IDEs, LSPs, and third-party tooling (OpenRewrite, Dependabot, AI coding agents, [starship](https://github.com/starship/starship/pull/7189), 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. I searched the Maven dev list archives for discussion on this feature, but I wasn't immediately able to find anything. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
