*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
You can take jetty example, no phase -> resolution -> failure if you use a
not resolvable version or whatever. If you put a phase which is not
"current" one then you get a passing build.
This is a very bad end user experience cause you fixed something by a
completely wrong solution IMHO.
Romain M
