-
Task
-
Resolution: Unresolved
-
Minor
Jenkins plugins use a custom version of the gmaven-plugin that hasn't been updated in years.
There is a gmavenplus-plugin that is maintained and is Java 11 compatible.
https://github.com/groovy/GMavenPlus
The pipeline-model-definition plugin recently switched to using gmavenplus with only some additional spotbugs issues.
Jenkins parent-pom should switch to gmavenplus and exclude gmaven.
Ideally only in a profile activated by the presence of Groovy sources.
Or just remove all support for Groovy from the parent POM, as it is a niche thing we do not really recommend. At least I would like to get rid of workflow-cps-plugin/src/test/groovy/ and its ilk. The main trouble with this option is that people do not read release notes when updating the parent POM (incl. most users of Dependabot), and in some cases a plugin using some Groovy would continue to compile yet be missing functionality—so we would either need to do a search for affected plugins, or introduce some kind of automated warning.