• gradle-jpi-plugin 0.36.0, gradle-plugin 1.36

      Installing Gradle plugin 1.29 shows these messages in the log on Jenkins 2.146(ish), emphasis mine:

      Oct 13, 2018 7:58:05 PM hudson.model.UpdateCenter$DownloadJob run
      INFO: Starting the installation of Gradle on behalf of admin
      Oct 13, 2018 7:58:05 PM hudson.model.UpdateCenter$UpdateCenterConfiguration download
      INFO: Downloading Gradle
      Oct 13, 2018 7:58:05 PM hudson.PluginManager dynamicLoad
      INFO: Attempting to dynamic load /…/plugins/gradle.jpi
      Oct 13, 2018 7:58:06 PM hudson.ClassicPluginStrategy createClassJarFromWebInfClasses
      WARNING: Created /…/plugins/gradle/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness

      Gradle plugin should update its toolchain to one supporting the newer classes.jar format. (Might be a problem with Gradle JPI Plugin, unsure).

      CC daspilker

          [JENKINS-54064] Gradle plugin uses legacy plugin format

          René Scheibe added a comment - - edited

          sghill I have seen you lately performed many changes on the gradle-jpi-pugin. Do you have an idea what this is exactly about and if the gradle-jpi-pugin or gradle-pugin has to be changed to fix the issue reported here?

          René Scheibe added a comment - - edited sghill I have seen you lately performed many changes on the gradle-jpi-pugin . Do you have an idea what this is exactly about and if the gradle-jpi-pugin or gradle-pugin has to be changed to fix the issue reported here?

          Daniel Beck added a comment -

          renescheibe It's a problem that manifests in Gradle Plugin (as reported) but if it's packaged using Gradle JPI Plugin, then the latter needs to be updated, or changed, to implement a change similar to https://github.com/jenkinsci/maven-hpi-plugin/commit/603535119122e820751607812bb7d0bd3b8c3556

          The corresponding core change is https://github.com/jenkinsci/jenkins/commit/f7330d7a158eff6705706b1f812993a9b918c351

          Basically, do not deliver a WEB-INF/classes directory, but a WEB-INF/${pluginName}.jar file.

          Daniel Beck added a comment - renescheibe It's a problem that manifests in Gradle Plugin (as reported) but if it's packaged using Gradle JPI Plugin, then the latter needs to be updated, or changed, to implement a change similar to https://github.com/jenkinsci/maven-hpi-plugin/commit/603535119122e820751607812bb7d0bd3b8c3556 The corresponding core change is https://github.com/jenkinsci/jenkins/commit/f7330d7a158eff6705706b1f812993a9b918c351 Basically, do not deliver a WEB-INF/classes directory, but a WEB-INF/${pluginName}.jar file.

          René Scheibe added a comment -

          danielbeck Thanks a lot for these very useful details.

          René Scheibe added a comment - danielbeck Thanks a lot for these very useful details.

          Steve Hill added a comment -

          This has been released in 0.36.0.

          Steve Hill added a comment - This has been released in 0.36.0 .

            Unassigned Unassigned
            danielbeck Daniel Beck
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: