Le 04/04/2026 à 21:41, Romain Manni-Bucau a écrit :
is using a property a bad idea?
Namespace is a XML concept which knows nothing about Maven properties. If you had another idea in mind, can you provide an example?
We must make model 4.1.0 not 4.0.0 by design.
Yes, but it does not require to change the namespace. This is similar to making a version 2 of a Java library: new version should not require to change the package name if all classes are compatible.
Using namespace doesn't go against xml at all
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.
Most of what was written is just technically wrong
This is a vague assertion. What exactly was wrong?
and has solution in maven and outside
The solution outside is to ignore namespace or use XSLT. The former has drawbacks (e.g. can't incorporate Maven POM in a larger XML document), the latter is possible is an additional difficulty for no technical reason other than history.
Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
