You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2025/03/20 19:38:00 UTC
[jira] [Commented] (MNG-8537) Maven 4 namespace should not change
[ https://issues.apache.org/jira/browse/MNG-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937208#comment-17937208 ]
Guillaume Nodet commented on MNG-8537:
--------------------------------------
I've create MNG-8639 to validate namespace consistency and enforce the use of a namespace when reading XML models with modelVersion > 4.0.0.
> Maven 4 namespace should not change
> -----------------------------------
>
> Key: MNG-8537
> URL: https://issues.apache.org/jira/browse/MNG-8537
> Project: Maven
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
>
> Just noticed that Maven 4 has a new namespace URL. The old namespace was
>
> [http://maven.apache.org/POM/4.0.0]
>
> The new one is
>
> [http://maven.apache.org/POM/4.1.0]
>
> Putting version numbers in namespaces is a known XML antipattern because it makes it extremely difficult and inconvenient to write tools that process both, even when they are much the same. XSLT, DOM, XQuery, JDOM, etc. — really any XML aware tool — is going to have problems with this.
> Model version 4.1.0 is not a new and different schema that completely breaks with the past. Most old elements from 4.0.0 are still present and still mean exactly the same thing: groupId, artifactId, name, dependency, and most others. There are new elements but that doesn't imply a new namespace. Adding a new namespace is asserting that all the elements are different.
> IMHO Maven 4 should not change the namespace URL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)