[JENKINS-58028] Move from gmaven-plugin to gmavenplus-plugin; or remove entirely

[jenkins-infra-bot]

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.

---

Originally reported by bitwiseman, imported from: Move from gmaven-plugin to gmavenplus-plugin; or remove entirely

• status: Open
• priority: Minor
• component(s): plugin-pom
• label(s): hacktoberfest
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20260108-221235

Raw content of original issue

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. 

[jenkins-infra-bot]

• Remote links associated with this issue:

  • pipeline-model-definition PR 337
  • pipeline-model-definition PR 340
  • jenkinsci/pom PR #​42
  • jenkinsci/plugin-pom PR #​209

[jenkins-infra-bot]

jglick:

• Original comment link
• Raw content of original comment:

  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.
  

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.

[jenkins-infra-bot]

bitwiseman:

• Original comment link
• Raw content of original comment:

  jglick 
  It seems like something we could find a way to produce a warning/error for - https://maven.apache.org/enforcer/enforcer-rules/bannedPlugins.html .
  We could make both available to start and then ban gmaven in a later release.
  
  I understand you have a strong opinion about how groovy should and should not be used in the project, but that is a much larger change.  This change, on the other hand, is almost a drop in replacement that unblocked one of our core plugins to build and run on Java 11.
  

jglick
It seems like something we could find a way to produce a warning/error for - https://maven.apache.org/enforcer/enforcer-rules/bannedPlugins.html .
We could make both available to start and then ban gmaven in a later release.

I understand you have a strong opinion about how groovy should and should not be used in the project, but that is a much larger change. This change, on the other hand, is almost a drop in replacement that unblocked one of our core plugins to build and run on Java 11.

[jenkins-infra-bot]

jglick:

• Original comment link
• Raw content of original comment:

  Hacktoberfest idea:
  
  	
  Translate all src/main/groovy/**/*.groovy to src/main/java/**/*.java in pipeline-model-definition modules. (Can be done incrementally, in dependency order.)
  	
  
  		
  Some but not most src/main/resources/**/*.groovy could also be translated: simple classes which do not need to be CPS-transformed.
  	
  	
  	
  Remove Groovy source support from plugin-pom, with a warning in the release notes that this would be incompatible for plugins out there which still build Groovy sources via Maven.
  
  
  
  Would reduce the maintenance burden on Declarative Pipeline somewhat, and generally reduce technical debt.
  
  References:
  
  	
  Rewrote CpsTransformer in Java for better speed and stack usage cloudbees/groovy-cps#59
  	
  Converted main sources from Groovy to Java groovy-sandbox#32
  	
  Bump gmavenplus-plugin from 1.9.1 to 1.10.0 #337 (comment)
  	
  Remove gmaven and groovy test workflow-cps-plugin#296 (review)
  
  
  

Hacktoberfest idea:

• Translate all src/main/groovy/**/*.groovy to src/main/java/**/*.java in pipeline-model-definition modules. (Can be done incrementally, in dependency order.)
  • Some but not most src/main/resources/**/*.groovy could also be translated: simple classes which do not need to be CPS-transformed.
• Remove Groovy source support from plugin-pom, with a warning in the release notes that this would be incompatible for plugins out there which still build Groovy sources via Maven.

Would reduce the maintenance burden on Declarative Pipeline somewhat, and generally reduce technical debt.

References:

• Rewrote CpsTransformer in Java for better speed and stack usage cloudbees/groovy-cps#59
• Converted main sources from Groovy to Java groovy-sandbox#32
• Bump gmavenplus-plugin from 1.9.1 to 1.10.0 #337 (comment)
• Remove gmaven and groovy test workflow-cps-plugin#296 (review)