I have looked into maven-polyglot before, and come to the conclusion that it is a proof of concept, and something that few if any people actually use, because:
1. Professional programmers are not actually offended by using XML in the POM, only novices would complain about such a thing. 2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, etc. If any of those things are able to handle a polyglot POM in non-XML, that's a tiny miracle. 3. maven-polyglot gets mentioned when people complain about Maven using XML, as 'look, you don't have to, you can use whatever you want' but no one actually does. 4. The first suspect when something doesn't work right in your build will always be maven-polyglot, because no one uses it, so it's potentially not compatible with every plugin. Then you get to convert back to pom.xml and try again. So better to skip the effort and stay with XML in the first place.
