You might be interested in https://basepom.github.io/
Delany
On Wed, 28 Jun 2023 at 08:40, Geoffrey De Smet
wrote:
> *Summary
> *
>
> Specifying the Java version (11, 17, ...)
> and latest maven plugin versions (compiler 3.11.0, surefire 3.1.2,
> failsafe, ...)
> in every pom is a tedious and br
Howdy,
Here is a PoC for import-plugins
https://github.com/apache/maven/pull/1190
T
On Wed, Jun 28, 2023 at 11:32 AM Geoffrey De Smet
wrote:
> Maybe we need a BOM import for all maven plugin versions instead?
>
> Currently all projects in the ASF forge have to individually
> update the compile
But, let's dream a bit (so all of this below is just a faint scratch, I do
not nor cannot state "we can do it in Maven4" :D ):
1. plugins:
A new Maven4 import scope, similar to "import", "import-plugins", that
would allow for your project to declare in depMgmt section to import
pluginMgt section o
Maybe we need a BOM import for all maven plugin versions instead?
Currently all projects in the ASF forge have to individually
update the compiler, surefire, ... plugin versions individually
and figure out which maven plugin versions are compatible.
With kind regards,
Geoffrey De Smet
---
Howdy,
This is an interesting idea, but IMHO without some "mixin" support, it
would work only for "shallow" (or flat?) kinds of projects
Forges like ASF (and Maven itself as part of ASF) have quite deep parent
POM hierarchy, and parents are not only about Java, as they also contain:
- deploym
*Summary
*
Specifying the Java version (11, 17, ...)
and latest maven plugin versions (compiler 3.11.0, surefire 3.1.2,
failsafe, ...)
in every pom is a tedious and brittle.
Existing parent poms are de-standarized and bloated.
This proposal solves that by introducing
a standardized parent pom
