I fully agree with the analysis
thinking at it, it seems we could provide a backward compatible option:
instead of changing pom.xml model to add more prerequisite features [1], why
don't we enhance META-INF/maven/plugin.xml [2] ?
Notice that, as I write that, I see that even maven version
Hi,
AFAIK there's no solution for it out of the box.
The pom model has no option to specify it, so it cannot be solved there.
The plugin descriptor is a Maven-only file, so that might work, but
requires Maven to understand it.
The other possible solution it to write an extension for it, which
How can I enforce that my custom Maven Plugin (or only a certain Mojo within)
is only executed with at least a certain Java version (i.e. Java8 due to the
use of class files being only compatible with Java8+). The prerequisites
section which seems like the natural way to define that only allows
