[
https://issues.apache.org/jira/browse/MNG-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937333#comment-17937333
]
Guillaume Nodet edited comment on MNG-8537 at 3/21/25 9:30 AM:
---------------------------------------------------------------
I don't think this is really achievable. We will probably release a subsequent
schema that will remove the deprecated elements. In addition having a fixed
namespace would require the parser to eventually be able to know which version
of the model is loaded. Unfortunately, the {{modelVersion}} is an element and
not an attribute, so it may be put at the very end of the xml. Plus the fact
that the poms uploaded with the 4.0.0 namespace may not even be XML
conformant...
was (Author: gnt):
I don't think this is really achievable. We will probably release a subsequent
schema that will remove the deprecated elements. In addition having a fixed
namespace would require the parser to eventually be able to know which version
of the model is loaded. Unfortunately, the {{modelVersion}} is an element and
not an attribute, so it may be put at the very end of the xml.
> 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
> Assignee: Guillaume Nodet
> 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)
