[gradle] 02/04: debian/gradle.1.md: Update man page to Gradle 2.5

[Kai-Chung Yan]

This is an automated email from the git hooks/post-receive script.

seamlik-guest pushed a commit to branch master
in repository gradle.

commit 349eed7a4e13de1fcc9c808e908089801cb688cb
Author: Kai-Chung Yan <seamlikok at gmail.com>
Date:   Wed Jul 8 17:23:31 2015 +0800

    debian/gradle.1.md: Update man page to Gradle 2.5
---
 debian/gradle.1.md | 47 +++++++++++++++++++++++++++--------------------
 1 file changed, 27 insertions(+), 20 deletions(-)

diff --git a/debian/gradle.1.md b/debian/gradle.1.md
index 31494ce..0cd1296 100644
--- a/debian/gradle.1.md
+++ b/debian/gradle.1.md
@@ -1,6 +1,6 @@
-% GRADLE(1) gradle 2.4-1 | Gradle Command Line Manual
+% GRADLE(1) gradle 2.5-1 | Gradle Command Line Manual
 % Gradle Depvelopers
-% 05 May 2015
+% 08 July 2015
 
 # NAME
 
@@ -31,6 +31,15 @@ gradle - A powerful build system for the JVM
 -c, --settings-file
 :   Specifies the settings file.
 
+--console
+:   Specifies which type of console output to generate.
+
+Set to **plain** to generate plain text only. This option disables all color and other rich output in the console output.
+
+Set to **auto** (the default) to enable color and other rich output in the console output when the build process is attached to a console, or to generate plain text only when not attached to a console.
+
+Set to **rich** to enable color and other rich output in the console output, regardless of whether the build process is not attached to a console. When not attached to a console, the build output will use ANSI control characters to generate the rich output.
+
 --continue
 :   Continues task execution after a task failure.
 
@@ -58,9 +67,6 @@ gradle - A powerful build system for the JVM
 -m, --dry-run
 :   Runs the build with all task actions disabled. See Section 11.7 of Gradle User Guide, "Dry Run".
 
---no-color
-:   Do not use color in the console output.
-
 --offline
 :   Specifies that the build should operate without accessing network resources. See Section 50.9.2 of Gradle User Guide, "Command line options to override caching".
 
@@ -73,8 +79,8 @@ gradle - A powerful build system for the JVM
 --parallel (incubating)
 :   Build projects in parallel. Gradle will attempt to determine the optimal number of executor threads to use. This option should only be used with decoupled projects (see Section 56.9 of Gradle User Guide, "Decoupled Projects").
 
---parallel-threads (incubating)
-:   Build projects in parallel, using the specified number of executor threads. For example **--parallel-threads=3**. This option should only be used with decoupled projects (see Section 56.9 of Gradle User Guide, "Decoupled Projects").
+--max-workers (incubating)
+:   Sets the maximum number of workers that Gradle may use. For example **--max-workers=3**. The default is the number of processors. This option replaces **--parallel-threads** when used in conjuction with **--parallel**.
 
 --profile
 :   Profiles build execution time and generates a report in the **buildDir/reports/profile** directory. See Section 11.6.7 of Gradle User Guide, "Profiling a build".
@@ -100,6 +106,9 @@ gradle - A powerful build system for the JVM
 -s, --stacktrace
 :   Print out the stacktrace also for user exceptions (e.g. compile error). See Chapter 18 of Gradle User Guide, "Logging".
 
+-t, --continuous (incubating)
+:   Enables continuous building - Gradle will automatically re-run when changes are detected.
+
 -u, --no-search-upwards
 :   Don't search in parent directories for a **settings.gradle** file.
 
@@ -113,23 +122,18 @@ The above information is printed to the console when you execute **gradle -h**.
 
 ## Deprecated options
 
-The following options are deprecated and will be removed in a future version of Gradle:
-
--C, --cache
-:   (deprecated) Specifies how compiled build scripts should be cached. Possible values are: **rebuild** or **on**. Default value is **on**. You should use **--recompile-scripts** instead.
-
---no-opt
-:   (deprecated) Specifies to ignore all task optimization. You should use **--rerun-tasks** instead.
+--no-color
+:   Do not use color in the console output. This option has been replaced by the **--console** plain option.
 
---refresh
-:   (deprecated) Refresh the state of resources of the type(s) specified. Currently only dependencies is supported. You should use **--refresh-dependencies** instead.
+--parallel-threads
+:   Build projects in parallel, using the specified number of executor threads. For example **--parallel-threads=3**. This option should only be used with decoupled projects (see Section 57.9 of Gradle User Guide, "Decoupled Projects"). This option has been replaced by **--max-workers**.
 
 ## Daemon options
 
-The Chapter 19 of Gradle User Guide, "The Gradle Daemon" contains more information about the daemon. For example it includes information how to turn on the daemon by default so that you can avoid using **--daemon** all the time.
+The Chapter 18 of Gradle User Guide, "The Gradle Daemon" contains more information about the daemon. For example it includes information how to turn on the daemon by default so that you can avoid using **--daemon** all the time.
 
 --daemon
-:   Uses the Gradle daemon to run the build. Starts the daemon if not running or existing daemon busy. Chapter 19 of Gradle User Guide, "The Gradle Daemon" contains more detailed information when new daemon processes are started.
+:   Uses the Gradle daemon to run the build. Starts the daemon if not running or existing daemon busy. Chapter 18 of Gradle User Guide, "The Gradle Daemon" contains more detailed information when new daemon processes are started.
 
 --foreground
 :   Starts the Gradle daemon in the foreground. Useful for debugging or troubleshooting because you can easily monitor the build execution.
@@ -157,8 +161,11 @@ GRADLE_OPTS
 :   Specifies command-line arguments to use to start the JVM. This can be useful for setting the system properties to use for running Gradle. For example you could set **GRADLE_OPTS="-Dorg.gradle.daemon=true"** to use the Gradle daemon without needing to use the **--daemon** option every time you run Gradle. Section 20.1 of Gradle User Guide, “Configuring the build environment via gradle.properties” contains more information about ways of configuring the daemon without using environmenta [...]
 
 GRADLE_USER_HOME
-: Specifies the Gradle user home directory.
+:   Specifies the Gradle user home directory (which defaults to **USER_HOME/.gradle** if not set).
+
+JAVA_HOME
+:   Specifies the JDK installation directory to use.
 
 # SEE ALSO
 
-/usr/share/doc/gradle/userguide/userguide.html
+https://docs.gradle.org/current/userguide/userguide.html

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/gradle.git