command line options for gradle

These are documented here


//version
gradle -v

//initialize a dir for gradle builds
gradle init

//See what tasks are available
gradle tasks

Just like init, boot strapping for other types of builds is important. here is a link

The init (task) sets up build directory structure


gradle init --type java-library
gradle init --type java-application

The list of available build types are documented here


-v is same as --version
-q is same as --quite

gradle -h

//or

gradle --help

What is the gradle daemon?

Search for: What is the gradle daemon?

Gradle daemon is documented here

When you try to build with gradle it starts a daemon program

Gradle runs on the Java Virtual Machine (JVM) and uses several supporting libraries that require a non-trivial initialization time. As a result, it can sometimes seem a little slow to start. The solution to this problem is the Gradle Daemon: a long-lived background process that executes your builds much more quickly than would otherwise be the case. We accomplish this by avoiding the expensive bootstrapping process as well as leveraging caching, by keeping data about your project in memory. Running Gradle builds with the Daemon is no different than without. Simply configure whether you want to use it or not - everything else is handled transparently by Gradle.


install-dir/.gradle/gradle.properties

org.gradle.daemon=false

gradle --stop

The Gradle Tooling API that is used by IDEs and other tools to integrate with Gradle always uses the Gradle Daemon to execute builds. If you are executing Gradle builds from within your IDE you are using the Gradle Daemon and do not need to enable it for your environment.

The tooling API is documented here

It is primarily used for programatical control of the gradle builds, as in IDEs.