Hi all,
My first thought is: "why?" What benefit would it give? A few lines less
XML in a POM? Less upgrades? I think most Maven users write their POM
once and then use tools like Dependabot or Renovate to keep the plugins
up-to-date.
Additionally, I have a few concerns with this idea.
1. As a Maven user, if one "part" breaks with an upgrade, you cannot
upgrade - this would prevent usage of new features inside other "parts"
that you could be waiting for.
2. As a Maven developer, wouldn't this new "all-in-one" plugin become an
unnecessary large codebase?
I'm not saying I agree or disagree; I'd first like to know the "why".
And I'm curious what your ideas are regarding the concerns I brought up.
Maarten
On 09/10/2026 02:36, Hervé Boutemy via dev wrote:
while we are discussing structural changes for Maven 4 longer term, I think
instead of maintaining these 4 core plugins in a 4.x branch for these base
clean/resources/install/deploy operations, it may be the right moment to
consolidate them into one single plugin
no idea how to call this plugin
with its clean, resources, testResources, copy-resources, install, install-
file, deploy and deploy-file goals
see https://maven.apache.org/plugins/
compiler, site and surefire as independent plugins, even when we'll do a 4.x
branch, remains IMHO more reasonable
WDYT?
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
