A plugin dependency depends on a more recent groovy version

[Valentin Delaye (jonesbusy)]

Hi,

I maintains artifactory-client-api-plugin (https://plugins.jenkins.io/artifactory-client-api/) which is an API plugin bundling https://github.com/jfrog/artifactory-client-java)

It's now used by consumer like artifactory-artifact-manager or jobcacher-artifactory-storage

The bundled library artifactory-client-java is implemented with a mix of Java and Groovy code (2.4.21). Until now no issue when using it in Jenkins

However some recent PR https://github.com/jfrog/artifactory-client-java/pull/394 upgraded the build to groovy 4.0.23

I did few tentative (exclusion), pluginFirstClassLoader, classMasking etc but I always end of with weird classpath error during execution of pipeline (like NoClassDefFoundError: org/codehaus/groovy/vmplugin/v8/IndyInterface).

Does anyone know if we faced similar issue when a plugin dependency bundle a more recent version of groovy ? Can we do something about it ?

Thanks for your tips!

Valentin

[Jesse Glick]

For general background: https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/

[Jenkins Developers]

Only way I was able to make it work is with `pluginFirstClassLoader` and packaging the groovy 4 as part of plugin artifact

This work on production and required to switch JenkinsRule to RealJenkinsRule for dependent tests (Only the using running pipelines jobs).

The last challenge is make the bom works. Some prep tests are using JenkinsRule

FTR: https://github.com/jenkinsci/artifactory-client-api-plugin/issues/100 and https://github.com/jenkinsci/bom/pull/6935

On Tuesday, November 12, 2024 at 11:46:42 PM UTC+1 jgl...@cloudbees.com wrote:

For general background: https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/