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.
JavaExec internal API spec seems to have changed in Gradle 6.6, making v1.7.0 fail
See original GitHub issueTrying to use application plugin with gradle-modules-plugin 1.7.0 and Gradle 6.6 causes a ReflectionException to be raised at ModularJavaExec (line 97). The Gradle internal API appears to have changed so that the line:
var hb = on(this).field("javaExecHandleBuilder").get();
fails to find the specified field (JavaExecAction javaExecHandleBuilder) as it no longer exists in the JavaExec class. It has been replaced by: DefaultJavaExecSpec javaExecSpec (which should, at first look, provide the same support for getExecutable() required by ModularJavaExec).
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@msgilligan @gwinstanley Thanks for the feedback! So it makes sense to further maintain this plugin. I will wait for a couple of weeks, in the hope that someone sends a pull request that is less hacky than mine. After that, I will make a patch release.
The workaround
modularity.disableEffectiveArgumentsAdjustment()worked with gradle 6.7 and also the openjfx plugin