[
https://issues.apache.org/jira/browse/MNG-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937461#comment-17937461
]
Guillaume Nodet commented on MNG-8537:
--------------------------------------
I think the major point here is the fact that the modelVersion may be set at
the end. So the parser would only know which model version is used at the end
? That's just not gonna work. Also I doubt Modello has been architected with
the ability to support that (though I may be wrong).
If modelVersion would be moved as an attribute, it may be possible to get that
working, but that will require a brand new namespace anyway. That one could be
made to not change in the future.
But please, be my guest, go ahead and fix the problem. You raised the issue 3
months ago, the new namespace has been introduced 18 months ago, and the
decision to version namespaces has been made 20 years ago, without actually
using the namespaces, having non conformant XML, etc...
I'm not sure I'm willing to spend a week of my time for that.
> 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)
