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 à 07:55, Mirko Friedenhagen a écrit : > I thought the idea of maven 4 was to prepare for faster moves and enabling breaking changes like e.g. one-line-gav definitions possibly with attributes. java.util to my knowledge never broke compatibility while javax/jakarta did so mostly for corporate licensing. Yes, this is the idea. The Maven 4 POM does not break compatibility compared to Maven 3 POM. It adds a few new elements, but did not changed the semantic of previous elements. This is equivalent to adding new classes in a package without breaking the existing classes. We don't rename package in such situation. The same argument applies to the XML namespace. Martin