Thanks!
Just here: https://issues.apache.org/jira/projects/NETBEANS/issues ? I
have to make an account? (didn't see add issue button)
FWIW: Got a reasonable solution that ties me over for now: made a Task
and just hard coded a specific spec name to that. It mostly works; and
available
I'd recommend to add an improvement request into JIRA. I do not think
that it can be solved in 11.3, some cumbersome workaround could be
overriding the test action.
Unfortunately 12.0 is almost ready so most probably this can be released
in August or some daily builds.
On 4/30/20 11:54 AM,
The older G4NB plugin had smarts or something such that it looked at
pathing of where a test file was and adjusted the gradle invocation
accordingly.
So for example, a Spock spec in:
src/test/groovy/com/blah/blah/SomeSpec.groovy
would invoke gradle a bit like like:
./gradlew tests --tests
