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, Fred Welland wrote:
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 com.blah.blah.SomeSpec
And if the Spock spec was here:
src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy
would invoke gradle a bit like like:
./gradlew integrationTest --tests com.blah.blah.OtherSpec
Basically, it seemed to do some simple matching of the path against
tasks in the build file and away it went.
Can the 11.3, using builtin gradle support support this kind of
behavior? If so how?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
