+1 for B, -1 for A for reasons I've been bringing up repeatedly for
the last six years or so, of which the most significant is being able
to use the large and rich XML toolbox to process POMs instead of
special purpose maven libraries.

I'll also note that people continue to create new reasons that simply
aren't true. In particular, consumer POMs stay in the
http://maven.apache.org/POM/4.0.0 namespace no matter what, (or at
least that's what I've been told repeatedly) so there is no option for
a "simplified consumer POM like: <project
xmlns="http://maven.apache.org/POM/4.1.0";>" The new namespace is only
for build POMs.

On Tue, Mar 31, 2026 at 9:22 PM Hervé Boutemy <[email protected]> wrote:
>
> after a long discussion on consequences of each choice, it's time to make a
> decision:
>
> option A:
> keep 4.1.0 XML namespace that permits modelVersion inference since 4.0.0-
> alpha-6
> = promote simplified consumer POM like:
> <project xmlns="http://maven.apache.org/POM/4.1.0";>
> ...
> </project>
>
>
> option B:
> revert to 4.0.0 XML namespace, forcing explicit modelVersion back:
> <project xmlns="http://maven.apache.org/POM/4.0.0";>
>   <modelVersion>4.1.0</modelVersion>
> ...
> </project>
> = finish the revert PR https://github.com/apache/maven/pull/10952
>
>
>
> no discussion please, even less digression, just a majority vote to make a
> final decision and let us work on the few other topics necessary to release
> Maven 4.0.0 after years of hard work.
>
>
> just a majority vote:
> A. <project xmlns="http://maven.apache.org/POM/4.1.0";>
> or
> B. <project xmlns="http://maven.apache.org/POM/4.0.0";>
>
> vote open for at least 72h
>
> Regards,
>
> Hervé
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


-- 
Elliotte Rusty Harold
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to