The project is configured to use the Gradle wrapper script to invoke Gradle build tool. Under normal conditions, Gradle doesn't have to be installed on the build system. The wrapper downloads the appropriate Gradle distribution automatically. However, there are cases when some extra steps must be taken, for example when the build system is placed in a controlled environment behind a firewall.
If the firewalled environment allows access to the public internet through a proxy, create the file gradle.properties in the project dir (or in the home dir) and set its content according to the following template.
systemProp.http.proxyHost=www.somehost.org systemProp.http.proxyPort=8080 systemProp.http.proxyUser=userid systemProp.http.proxyPassword=password systemProp.http.nonProxyHosts=localhost
More details can be found at https://docs.gradle.org/current/userguide/build_environment.html#sec:accessing_the_web_via_a_proxy.
If the firewalled environment doesn't allow access to the public internet through a proxy then Gradle must be installed on the build system manually. Follow the official Gradle installation guide at https://docs.gradle.org/current/userguide/installation.html and install Gradle on the target system. With Gradle installed manually all build commands must not be invoked through the Gradle wrapper. In other words, do not use the gradlew command but instead use gradle.
If you are in a restricted environment you may need to download the project dependencies manually. If so download the dependencies in local-repo/ form and then unzip it into the p2j/ directory. This contains all the jar files needed by the build and to run FWD. If you are using a FWD build that is different from the current latest available snapshot, then you should download the dependencies zip associated with that specific build. Do not use dependencies that are meant for a different FWD version.
The supported Gradle version is 3.x.