I agree with Roman. I do not oppose to this change in order to not block
more important work, but I do believe that this change will cause more
harm than good. We want to encourage migration to Maven 4. The branches
renaming will confuse Maven contributors who are not following this
thread. It would be worth if this change was for the years to come. But
it is only a temporary change to be reverted in maybe 6 months, thus
creating more confusion again when we will switch `master` back to Maven
4. Furthermore, it would be inconsistent with the `master` branch of
Maven core. If we keep the branches as they stand today, we may have a
period of 6 months where the `master` branch of some plugins do not
target the officially released Maven version, but is it really worth to
create this disturbance twice for such relatively short period?
Martin
Le 10/10/2026 à 09:27, Romain Manni-Bucau a écrit :
Issue is that you impact contributors and not really solve the underlying
issue. From my window it is a quick and dirty workaround with contributors
impact.
Nothing not doable but think skipping it is worth it and solving the
actually issue we are already facing would benefit the project and
community rather than a task for nothing.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
