On Sat, Feb 14, 2026 at 8:25 PM Romain Manni-Bucau <[email protected]> wrote: > > Hi > > My 2cts would be > > 1. this is the whole goal of the consumer pom work did in maven 3 so the > correct phrasing is "we must come with a new namespace", what is also true > is "we must support maven 4.0.0 model version and older namespace" => we > are good
No, that is the concern and that is not a resolution. The goal is to be able to use XML tools like XPath and XSLT to process pom files, both inside and outside Maven itself. By changing the namespace this becomes immensely more difficult because instead of adding a few new elements it's like we threw away all the existing elements and replaced every one with a new element. But this is not what we have done, or at least not what we should do. A group element is still a group element. A dependency element is still a dependency element. And so forth. These elements haven't changed so their names shouldn't have changed, and that includes the namespace. Many developers still confuse namespaces with schema versions, but that is not how namespaces were designed to work. In general the namespace should not change simply because a new version of a vocabulary has been released. In Maven's case that's what modelVersion is for. Releasing a new version of a vocabulary does not justify changing the namespace, and there is a large cost associated with doing so. -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
