Why does my plugin not build with java 21

[Fritz Elfert]

Hi,

I am struggling to find the reason for this build failure

https://ci.jenkins.io/job/Plugins/job/jclouds-plugin/job/PR-174/1/console

To me, this looks like the cloudbees maven-license-plugin fails to execute.
According to the message before the failure, ths plugin is used as version 1.15.
And when buildding locally with mvn -X, ith reveals, that there seems to be a groovy
script involved in perfoming the filter task of licenses which appears to be the culprit.
My guess is: that plugin is too old to handle java-21 class files.

I have looked at (working) build logs from another plugin here:

https://ci.jenkins.io/job/Plugins/job/config-file-provider-plugin/job/master/280/console

There, a completely different license plugin version (license:165.v7e11f4e4a_325) is used
which does not seem to have problems with java-21 class files.

What I don't understand:
I tried to use the same baseline/bom, but when I build locally with java-21, then this
has no effect on the license-plugin version being used (my build still uses 1.15)

Can somebody please explain what is going on here?

Thanks
-Fritz

[Mark Waite]

On Saturday, February 8, 2025 at 9:44:14 AM UTC-7 Fritz wrote:

Hi,

I am struggling to find the reason for this build failure

https://ci.jenkins.io/job/Plugins/job/jclouds-plugin/job/PR-174/1/console

I think that the plugin parent pom that you have specified is too old.  Use plugin parent pom 4.88 instead of 4.68.

Mark Waite

[Mark Waite]

In this specific case, the issue may have been resolved in https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.70 where the changelog says:

• Adapt maven-license-plugin changes (#801) @NotMyFault
  See https://github.com/jenkinsci/license-maven-plugin/releases/tag/98.vd05d703fe349