> Am 04.04.2026 um 22:37 schrieb Martin Desruisseaux via dev > <[email protected]>: > Namespaces are not intended to be a way to identify the version. Again, this > is similar to Java packages. We don't rename "java.util" to a new name > ("java.util.v21", "java.util.v22") every time that a new Java version is > released. 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. Mit freundlichen Grüßen Mirko Friedenhagen — --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
- Re: Maven 4.0.0 namespace from an XML perspect... Romain Manni-Bucau
- Re: Maven 4.0.0 namespace from an XML per... Martin Desruisseaux via dev
- Re: Maven 4.0.0 namespace from an XML perspect... Martin Desruisseaux via dev
- Re: Maven 4.0.0 namespace from an XML per... Chris Lafren
- Re: Maven 4.0.0 namespace from an XML... Martin Desruisseaux via dev
- Re: Maven 4.0.0 namespace from an... Gary Gregory
- Re: Maven 4.0.0 namespace fro... Jeff Jensen via dev
- Re: Maven 4.0.0 namespace fro... David Jencks
- Re: Maven 4.0.0 namespac... Romain Manni-Bucau
- Re: Maven 4.0.0 name... Martin Desruisseaux via dev
- Re: Maven 4.0.0 name... Mirko Friedenhagen
- Re: Maven 4.0.0 name... Martin Desruisseaux via dev
- Re: Maven 4.0.0 name... Romain Manni-Bucau
- Re: Maven 4.0.0 name... Martin Desruisseaux via dev
- Re: Maven 4.0.0 name... Romain Manni-Bucau
