Attila Kelemen

I'm not exactly sure but I remember if something like this was fixed in master. Can you try building the plugin from the sources and see if you still have...

I have debugged this issue (while also looking at the sources of NB) and I'm not sure that this issue is directly caused by this plugin. However, I have to...

I do not have the sources of "xmlpull" but created one manually and cannot reproduce this issue. Do you have any plugin installed which is not bundled with NB (other...

Ok, if you ever experience this issue again: Please reopen as I'm curious what could have caused this behaviour.

Can you share a project on GitHub with which you can reproduce the issue with? Because I have never experienced this issue and have no idea how this could happen....

It is technically possible to do this by creating a custom `run` task like this: ``` task run(dependsOn: classes, type: JavaExec) { main = project.hasProperty('mainClass') ? project.mainClass : '' classpath...

The same except that you need to also set `debug = true`.

@aplatypus yes, because [Test](https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/testing/Test.html) task also has a `workingDir` property.

I don't think (though I might be mistaken) that this requires any support from this plugin. You simply have to add this check to your build as described here: https://checkerframework.org/manual/#gradle...

If you do it in the way they said, there is no chance a tool would realize that you have this dependency. There is a workaround which might work (I...