Guillaume Nodet

I think this is because you're using an outdated version of Maven: ``` > mvn help:evaluate -Dexpression=project.artifactId -V Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) Maven home: /Users/gnodet/.sdkman/candidates/maven/3 Java version: 21.0.9, vendor: Oracle...

See https://github.com/apache/maven/issues/8457

> We do want to restrict namespaces when parsing 4.0.0 files to only the specifically allowed namespaces and no namespace at all. But we should not allow arbitrary strings. We...

> I've been pushing this for a long time, and the longer we wait the harder it gets to do. I'm not sure it can be done in 5.0 A...

@cstamas That was not really intended. I forgot to switch to the `mvnd-1.x` branch before running the publish scripts. I've reverted the change.

> I think we should reject any project that mixes `` and `` elements, I don't see that as a valid use case. I think this should even be done...

@Bananeweizen which version of `mvnd` ? 1.x or 2.x or both ?

Caused by https://github.com/apache/maven/commit/ddc228e958b4b7bfa93d080943d8a17268c4c512#diff-45a55c3ed6149aae9068fbf5a8cc3ce8a229d27a96ecfaf900922959afe53454 @cstamas it's only called by test inside maven with a null argument. I suppose `mvnd` does use it. Maybe we should add the previous constructor back ?

> Computers exist to automate, not incur additional labor. > > The JVM already has fairly standard parameters to configure transport details. Other Java components already follow them. Maven is...

> I was pleasantly surprised that this test passed. Things have been improved a lot in Maven 4...