[
https://issues.apache.org/jira/browse/MNG-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937500#comment-17937500
]
Guillaume Nodet commented on MNG-8537:
--------------------------------------
Yes, well, a first step will be available once 4.0 is released: we'll have a
new namespace that all 4.1.0 model will use and they will be XML conformant.
I'd like to be able to validate any POM before it's synced to Central, but we
need to ask Sonatype if that's doable. The problem is that Maven produced POMs
will most probably be fine, but we have no control over the ones generated by
gradle or any other tool. So xml conformance and the namespace need to be
enforced in Central, not only in Maven itself.
> 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: 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)
