[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format

dbeck@cloudbees.com (JIRA)

unread,

Oct 13, 2018, 4:44:02 PM10/13/18

to jenkinsc...@googlegroups.com

Daniel Beck created an issue

Jenkins /

JENKINS-54064

Gradle plugin uses legacy plugin format

Issue Type:	Bug
Assignee:	Stefan Wolf
Components:	gradle-plugin
Created:	2018-10-13 20:43
Priority:	Minor
Reporter:	Daniel Beck

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 Daniel Spilker

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

rene.scheibe@gmail.com (JIRA)

unread,

Dec 15, 2019, 9:31:03 AM12/15/19

to jenkinsc...@googlegroups.com

René Scheibe commented on

JENKINS-54064

Re: Gradle plugin uses legacy plugin format

Steve Hill 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 change to fix the issue reported here?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

rene.scheibe@gmail.com (JIRA)

unread,

Dec 15, 2019, 9:32:02 AM12/15/19

to jenkinsc...@googlegroups.com

René Scheibe edited a comment on

JENKINS-54064

Re: Gradle plugin uses legacy plugin format

[~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 change changed to fix the issue reported here?

Add Comment

dbeck@cloudbees.com (JIRA)

unread,

Dec 16, 2019, 3:32:03 AM12/16/19

to jenkinsc...@googlegroups.com

Daniel Beck commented on

JENKINS-54064

Re: Gradle plugin uses legacy plugin format

René Scheibe 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.