The wrapper script works just like the gradle command but uses the gradle version specified by the project.
See https://docs.gradle.org/current/userguide/gradle_wrapper.html <https://docs.gradle.org/current/userguide/gradle_wrapper.html> > On Oct 31, 2019, at 9:58 AM, Jeanette Winzenburg <faste...@swingempire.de> > wrote: > > > Zitat von Nir Lisker <nlis...@gmail.com>: > >> Did you run the wrapper with gradlew or just gradle? The latter uses the >> "global" version installed on the OS which might not be up to date (use >> 'gradle --version' to check). >> > > > in my cygwin console I type: > > gradle > > and get the error message .. hmm ... so, yeah seems to be global version > that's out of date. > > Are you saying that using gradlew (*cough - how exactly?) would keep the > required version up-to-date? > > Thanks > Jeanette > >> - Nir >> >> On Thu, Oct 31, 2019 at 3:41 PM Jeanette Winzenburg <faste...@swingempire.de> >> wrote: >> >>> >>> .. fails (gradle run from cygwin console) with: >>> >>> * Where: >>> Build file >>> 'C:\Daten\data-for-work\eclipse\gitrep-openjdk\jfx-fork\build.gradle' >>> line: 250 >>> >>> * What went wrong: >>> A problem occurred evaluating root project 'jfx-fork'. >>> > FAIL: Gradle version too old: 4.10.2; must be at least 5.3 >>> >>> which is rather clear in itself, but ... how to update? It seems to >>> too nothing, not even list the tasks >>> >>> CU, Jeanette >>>
