Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using Gradle 4.x's implementation configuration results in runtime exceptions

See original GitHub issue

I set up the project using the sample project and using the latest Gradle (4.9): https://docs.gradle.org/4.9/userguide/java_plugin.html#sec:java_plugin_and_dependency_management

compile is deprecated since 4.0, but this plugin still relies on it and doesn’t work if using the new replacement configuration implementation. The server started up with jettyRun but when I tried to do any operations on it it crashed with ClassNotFoundExceptions. After changing all my implementations to compile it started working.

Note: providedCompile should also be the new compileOnly configuration.

Since the Gradle requirements are “2.0.0 + | 4.0 or newer”, it should support this feature.

Issue Analytics

State:
Created 5 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

TWiStErRobcommented, Sep 1, 2018

(I’m migrating from AppEngine 1.8.11 with Eclipse plugin to latest with Gradle/IDEA due to Java 7 deprecation; back then there was no standard/flexible as far as I remember)

0reactions

loosebazookacommented, Sep 18, 2018

@parkjam4 looks like gretty is being maintined in a new repository github.com/gretty-gradle-plugin, I’m going to see if that plugin works with gradle 4.x