-
Notifications
You must be signed in to change notification settings - Fork 113
Gradle 6.0.1 Build Failed #177
Comments
It looks like this only needs a new release, the changes are already made. For now I just added the jar locally (like so) |
we a Gradle rollback 5.6.2 |
Any estimated time for this release? |
Release needed! |
Any ETA for a release that fixes this issue? |
Waiting for new release... |
Yes, release needed, please :) |
@rnentjes 2.14.2-SNAPSHOT source is where ? |
@i-hyun Just check out the repository and build it yourself |
@rnentjes oh, checked X) |
I solved this issue switching to webpack and calling it in a custom gradle task: task webpackBuild(type: Exec) {
workingDir 'base/path'
commandLine 'npm', 'run', 'build'
} |
(jk) We may find solution to Covid-19 in a year but this project getting released in this timeframe is a far fetched thought. |
Anyone that knows a workaround? |
I got this js and the corresponding css plugin running with gradle 6.6.1 See my comment eriwen/gradle-css-plugin#58 (comment) for instructions. No modification is needed, just clone, build and use at your gradle script |
I forked and built the master branch with minor modifications. Some unit tests fail but minification works for me. |
I went down the webpack rabbit hole only to find pain and sorrow. I suggest that, if you want to use a non-java minifier, you try Terser instead https://www.npmjs.com/package/terser which is what webpack uses. Besides, with webpack you may actually end up with a larger file than the original...
|
Looks like this issue affects Gradle 7.+ as well (tested on 7.0.2 & 7.1.1) |
For those looking for a similar solution which supports Gradle 6+, I migrated to: |
Releases were broken with the previous version of the JPI plugin [0], therefore we needed to try upgrading to the latest version. As the latest version requires Gradle 6, we have a few changes to make: - `jenkinsVersion` needs to be referenced through `project.properties` - the `war` plugin needs to be explicitly added - the CSS/JS plugins we're using are not yet released[1][2], so we can follow the tricks in Spotless[3] to use the version from the (pinned) latest commit on GitHub Next, as we're upgrading the JPI plugin, we need to: - migrate to using `implementation` / `testImplementation` - add Feature Variants for each of the `optionalJenkinsPlugins` - although I'm not sure if they're needed right now, we'll produce them for now and review later See also https://groups.google.com/g/jenkinsci-dev/c/CDVvgj9dDMs [0]: jenkinsci/gradle-jpi-plugin#192 [1]: eriwen/gradle-css-plugin#58 [2]: eriwen/gradle-js-plugin#177 [3]: https://github.com/diffplug/spotless/blob/a7f25eb51c6d4006591ea911157e62d0213e320b/CONTRIBUTING.md
Note that building the JAR yourself isn't necessarily required - see jenkinsci/job-dsl-plugin@6b7a8d8 for how I used the JitPack service |
today gradle 5.6.2 to 6.0.1 upgrade
but 6.0.1 build fail a plugin
* What went wrong:
An exception occurred applying plugin request [id: 'com.eriwen.gradle.js', version: '2.14.1']
> Failed to apply plugin [id 'com.eriwen.gradle.js']
> Could not create an instance of type com.eriwen.gradle.js.JavaScriptExtension.
> Could not create an instance of type com.eriwen.gradle.js.source.internal.DefaultJavaScriptSourceSetContainer.
> org.gradle.api.internal.AbstractNamedDomainObjectContainer: method <init>(Ljava/lang/Class;Lorg/gradle/internal/reflect/Instantiator;)V not found
* Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Thanks in advance.
The text was updated successfully, but these errors were encountered: