Hello Mathias
Thanks for creating this list. On the "blockers with no known
workaround" item, I have this pull request which could be merged if
approved. It applies only to projects using module source hierarchy.
Classical Maven projects are not impacted, so this change should not be
visible to the vast majority of current users. But it is necessary for
continuing the work on module hierarchy at the Maven JAR plugin level.
https://github.com/apache/maven/pull/11639
And the following pull request is needed for resources management.
Again, it applies only to projects using module source hierarchy. Maybe
more important, it also checks that a modular project is not malformed.
I think that it is better to be strict at GA release time rather than
making the checks stricter in a subsequent release, which could be a
compatibility break:
https://github.com/apache/maven/pull/11700
Thanks,
Martin
Le 12/02/2026 à 18:10, Matthias Bünger a écrit :
Good evening everybody,
last week a small number of commiter and PMC had a chat about the
current situation about Maven 4.0.0.
Nobody of the people attended was aware of any outstanding blocking
issues, but also nobody could precicle say what else needs to be done
for a GA release. As a result we collected some points on a wiki page
[1].
Today Benjamin asked me to send a mail to the list, to gather
feedback, if we missed anything . Do you agree with the points on the
list or do you see any (and if yes, which) blocker that needs to be
done, before we can consider a 4.0.0 GA?
Please note: This discussion should focus on "What's need to be done
for 4.0.0". It's not about discussions about will there new RC or was
RC5 the last RC. This can be discussed when we have a complete (as
possible) list of TO-DO's. So please avoid to restart any discussion
about alpha/beta/RC versions in this thread. What happend, happend
(including new features, like Maven Update tool, during RC phase) -
thank you.
Matthias
[1]:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0+GA+checklist
