Re: Maven 4.0.0 namespace from an XML perspective
"Martin Desruisseaux via dev" <[email protected]>
| Newsgroups | gmane.comp.jakarta.turbine.maven.devel |
|---|---|
| Message-ID | <[email protected]> |
Le 05/04/2026 à 16:19, Romain Manni-Bucau a écrit : > side note: I can hear we mitigate the breaking changes now and keep it > for next time but it is going back to fall from higher later so we > must decide now how we'll solve the drop of <module> now IMHO and > namespace/modelVersion is a clean way to do it. Yes, but whether we change the namespace for Maven 4 does not impact whether we will need to do another change for Maven 5. If the POM schema of Maven 5 has incompatible changes compared to any previous versions, including Maven 4, we will need to consider a namespace change anyway. Changing the namespace of Maven 4 will not give us more flexibility for Maven 5. Like Java packages, as long as the changes are compatible, we keep the same namespace. We should change the namespace only the first time that a version is released with incompatible changes. This is not yet the case of Maven 4. Martin