-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE after upgrade to 1.6.5 #61
Comments
Hi @xenoterracide. I forked your repo and am trying to reproduce this locally. In order to debug one of the failing test methods such as Kaboom -> apparently GradleRunner is not debuggable when used with kotlin 🤦♂️ gradle/gradle#6862 So while the test So let's keep in touch on this. I'm using tag v0.6.4 of your project and JDK 9.0.4. |
OK, I troubleshot @xenoterracide 's failing build. I don't understand the root cause yet, but I at least have a workaround. Apply this snippet to a failing Kotlin buildscript: tasks.named<com.github.spotbugs.SpotBugsTask>("spotbugsMain") {
reports.xml.setEnabled(true)
} (In @xenoterracide 's case, I applied this to tl;dr The root cause is that In the meantime, I'll do two things:
|
…tBugsTask is not configured - This shouldn't ever happen; it might be related to the way Kotlin buildscripts apply plugins? - Also added a Kotlin buildscript-based simple sanity test Signed-off-by: Kyle Moore <github@kylemoore.com>
you can see a failing test run/sha1 here https://bitbucket.org/xenoterracide/gradle-plugin-bundle/addon/pipelines/home#!/results/151/steps/%7Be81a5008-881e-4999-b806-9db81e9e2113%7D
The text was updated successfully, but these errors were encountered: