Gradle wrapper weird behaviour (FIXED)

(Augusto Ribeiro) #1


My gradle wrapper has some weird behaviour, different from my colleagues. Every time I pass a parameter gradle wrapper seems to interpret it as task name always. I am running gradle wrapper in a terminal in MacOS High Sierra (10.13.2).

./gradlew build --stacktrace

FAILURE: Build failed with an exception.

* What went wrong:
Task '--stacktrace' not found in project ':content-processing'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at


Anyone experienced something similar? My colleges seem to not experience the same.

EDIT: it seems like ./gradlew works on a subfolder but it fails to understand the ‘–options’ but if I use it from the root it seems to understand it. So if I want to build from the subfolder using ‘…/gradlew --stacktrace’ seems to work