Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69699

Update plugin to newer harness for ClassicPluginStrategy

XMLWordPrintable

    • 1.1

      WARNING hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /opt/app/jenkins/plugins/JDK_Parameter_Plugin/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness

          [JENKINS-69699] Update plugin to newer harness for ClassicPluginStrategy

          Lou Fiorino created issue -

          Mark Waite added a comment -

          Thanks for the report lfiorino.

          The plugin has a known security issue. Using a plugin with a known security issue is a much higher risk than any risk from the warning message.

          The warning can be resolved by fixing the security issue and by following the "update parent pom" and "update Jenkins version" steps in the "Improve a plugin" tutorial. Are you interested in adopting the plugin so that the warning can be resolved?

          The plugin was last released 9 years ago. Unless someone adopts it, the warning and the security issue are not likely to ever be fixed.

          As another alternative, you could uninstall the plugin and use the Eclipse Temurin JDK tool installer or the JDK tool installer. That provides a selection in the job definition that will choose the JDK. If users need to choose a specific JDK, then you could parameterize the job, present the list of JDK's, and use the tool statement in declarative Pipeline to use that Java version.

          Mark Waite added a comment - Thanks for the report lfiorino . The plugin has a known security issue. Using a plugin with a known security issue is a much higher risk than any risk from the warning message. The warning can be resolved by fixing the security issue and by following the "update parent pom" and "update Jenkins version" steps in the "Improve a plugin" tutorial. Are you interested in adopting the plugin so that the warning can be resolved? The plugin was last released 9 years ago. Unless someone adopts it, the warning and the security issue are not likely to ever be fixed. As another alternative, you could uninstall the plugin and use the Eclipse Temurin JDK tool installer or the JDK tool installer. That provides a selection in the job definition that will choose the JDK. If users need to choose a specific JDK, then you could parameterize the job, present the list of JDK's, and use the tool statement in declarative Pipeline to use that Java version.
          Mark Waite made changes -
          Released As New: 1.1
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            lfiorino Lou Fiorino
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: