Open reinholdfuereder opened 9 years ago
Hm, the test now also seems to hang in cygwin cmd line (at the end of the last test) so that I need to kill the gradle daemon process that is then still around (shown in ProcessExplorer hierarchy in level 0, i.e. without parent, and in fact its parent process is no more alive/around). Not sure why/when it worked before.
While my gradle plug-in (note that it internally depends/requires some project configuration resolving) worked in real usage, it failed in nebula-test.
Interesting part of my plug-in's build.gradle file:
With some dirty temp custom gradle plug-in/task adaptions I get some pointer to the root cause:
Sounds very much related to:
I tried the suggested workaround of "fork = true" (maybe note that I am on Windows using IntelliJ IDEA):
Because the original problem was a classloader issue, the following workaround based on the aforementioned github issues helps from within IDEA (i.e. without forking), but is IMHO very ugly (and it was non-obvious and time consuming and seemingly others have similar problems?):