How shall we deal with the traditional commands: ./gradlew test and ./gradlew build

The question is what is our suggestions to deal with these commands, ./gradlew test and ./gradlew build? If we are still in favor of them, can we overwrite them by calling the current ./gradlew goTest and ./gradlew compile. If we are not in favor of them, is there a way to remove or inhibit them?

@jonpspri Could you look at this question, as the expert of gogradle? Thx.

When we run the commands, ./gradlew test and ./gradlew build, brought in by gogradle plugin, the test cases under openwhisk/test will be running as below:

```
Step 1/3 : FROM dockerskeleton
---> b87a7e46c988
Step 2/3 : ENV FLASK_PROXY_PORT 8080
---> Using cache
---> f6a1758b06ff
Step 3/3 : CMD ["/bin/bash", "-c", "tail -f /dev/null"]
---> Using cache
---> c7a6360cc3aa
Successfully built c7a6360cc3aa
Successfully tagged badproxy:latest

> Task :tests:dat:blackbox:badproxy:distDocker
Fri Jan 26 09:59:23 EST 2018: Executing 'docker build -t badproxy /Users/vincent/workspace/openwhisk/tests/dat/blackbox/badproxy'
Building 'badproxy' took 0.168 seconds

> Task :tests:dat:blackbox:badproxy:tagImage
Fri Jan 26 09:59:23 EST 2018: Executing 'docker tag badproxy whisk/badproxy:latest'
<========-----> 66% EXECUTING [9s]
> :clitests:test > 0 tests completed
> :clitests:test > Executing test actionContainers.ActionProxyContainerTests
```

Test cases of scala in openwhisk-cli still depends on the scala code under openwhisk/test. I think that is the reason for this behavior.