gdub
gdub copied to clipboard
gw: always execute from same dir that gradle or gradlew would (#22)
This PR addresses #22:
- Commit 1
- adds a gradle build for
gw
itself, just as a convenient way of running some script-tests. - adds a Travis build for running those tests.
- adds test which run both before and after a gradle-wrapper is installed, testing
gradle
andgradlew
wrapping behaviour. The test fails - it is testing that the correct subproject task is executed in a subproject without abuild.gradle
, and checks the behaviour is the same for all four ofgradle
,gradlew
,gw
->gradle
,gw
->gradlew
.
- adds a gradle build for
- Commit 2 fixes by removing the
cd
to the closest ancestor dir with abuild.gradle
.
In a properly constructed multi-project Gradle project this should make no difference - Gradle doesn't require you to run -b ../../......../build.gradle
and gw
should not assume you want to run from the rootProject, because neither gradle
nor gradlew
do.
Seems like this is already changed.