Gradle Command Line: Difference between revisions
No edit summary |
|||
(13 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
In case of a multi-project, Gradle command can be executed from the root of the project or from any sub-projects. | In case of a multi-project, Gradle command can be executed from the root of the project or from any sub-projects. | ||
Some command line options have the same effect as setting corresponding properties or environment variables. When a command line option is present, it has precedence over the equivalent properties or environment variables. More details in: {{Internal|Gradle_Variables_and_Properties#Command_Line_Flags|Gradle Variables and Properties}} | |||
=Command Line Flags= | =Command Line Flags= | ||
==--help== | ==<tt>--help</tt>== | ||
In-line help. | In-line help. | ||
==--version== | <syntaxhighlight lang='bash'> | ||
gradle --help | |||
</syntaxhighlight> | |||
==<tt>--version</tt>== | |||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
./gradlew --version | ./gradlew --version | ||
Line 18: | Line 24: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==--q,--quiet== | ==<tt>--q</tt>,<tt>--quiet</tt>== | ||
Only warning and error category output is displayed. The logger "quiet" category can be accessed with: | Only warning and error category output is displayed. The logger "quiet" category can be accessed with: | ||
<syntaxhighlight lang='groovy'> | <syntaxhighlight lang='groovy'> | ||
Line 24: | Line 30: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | ||
==-m,--dry-run== | ==<tt>-m</tt>,<tt>--dry-run</tt>== | ||
Executes a [[Gradle_Task#Dry_Run|dry run]]: run the builds with all task actions disabled. | |||
==-i,--info== | |||
==<tt>-i</tt>,<tt>--info</tt>== | |||
When executed with -i, Gradle displays the tasks that are executed, in the order in which they are executed. Additionally, [[#-m.2C--dry-run|-m|--dry-run]] can be used to simulate the execution without actually performing the task actions. | When executed with -i, Gradle displays the tasks that are executed, in the order in which they are executed. Additionally, [[#-m.2C--dry-run|-m|--dry-run]] can be used to simulate the execution without actually performing the task actions. | ||
Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | ||
==<tt>-d</tt>,<tt>--debug</tt>== | |||
==-d,--debug== | |||
Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | Also see: {{Internal|Gradle Logging#Output_Configuration|Gradle Logging}} | ||
==-P<property-name>=<property-value> Project Properties== | ==<tt>-P<property-name>=<property-value></tt> Project Properties== | ||
See: {{Internal|Gradle_Project_Coordinates,_State_and_Configured_Properties#-P_Command-Line_Options|Gradle Project Coordinates, State and Configured Properties}} | See: {{Internal|Gradle_Project_Coordinates,_State_and_Configured_Properties#-P_Command-Line_Options|Gradle Project Coordinates, State and Configured Properties}} | ||
==-D<property-name>=<property-value> System Properties== | ==<tt>-D<property-name>=<property-value></tt> System Properties== | ||
See: {{Internal|Gradle System Properties#Overview|Gradle System Properties}} | See: {{Internal|Gradle System Properties#Overview|Gradle System Properties}} | ||
==<span id='-x'></span>-x,--exclude-task== | ==<span id='-x'></span>-x,--exclude-task== | ||
Line 47: | Line 53: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==--build-cache== | ==<tt>--build-cache</tt>== | ||
==--continue== | ==<tt>--continue</tt>== | ||
Also see [[Gradle_Task_Dependencies_and_Ordering#continue|Ordering Tasks]]. | Also see [[Gradle_Task_Dependencies_and_Ordering#continue|Ordering Tasks]]. | ||
==--no-daemon== | ==<tt>--no-daemon</tt>== | ||
See: {{Internal|Gradle Daemon|Gradle Daemon}} | See: {{Internal|Gradle Daemon|Gradle Daemon}} | ||
==<tt>--stop</tt>== | |||
See: {{Internal|Gradle_Daemon_Operations#Stop|Gradle Daemon Operations | Stop}} | |||
==<tt>--status</tt>== | |||
See: {{Internal|Gradle_Daemon_Operations#Status|Gradle Daemon Operations | Status}} | |||
==<tt>--refresh-dependencies</tt>== | |||
{{Internal|Gradle_Dependencies_and_Dependency_Configurations#Forced_Cache_Update|Gradle Dependencies and Dependency Configurations | Forced Cache Update}} | |||
==<tt>--rerun-tasks</tt>== | |||
{{Internal|Gradle_Incremental_Builds#Disable_Incremental_Builds|Disable Incremental Builds}} | |||
=Built-in Tasks= | =Built-in Tasks= | ||
* [[Gradle tasks Task|gradle tasks]] | * [[Gradle tasks Task|gradle tasks]] | ||
* [[Gradle Wrapper Operations|gradle wrapper]] | |||
* [[gradle init|gradle init]] |
Latest revision as of 05:18, 13 June 2021
Internal
Overview
In case of a multi-project, Gradle command can be executed from the root of the project or from any sub-projects.
Some command line options have the same effect as setting corresponding properties or environment variables. When a command line option is present, it has precedence over the equivalent properties or environment variables. More details in:
Command Line Flags
--help
In-line help.
gradle --help
--version
./gradlew --version
gradle --version
--q,--quiet
Only warning and error category output is displayed. The logger "quiet" category can be accessed with:
logger.quiet "will be displayed even in quiet mode"
Also see:
-m,--dry-run
Executes a dry run: run the builds with all task actions disabled.
-i,--info
When executed with -i, Gradle displays the tasks that are executed, in the order in which they are executed. Additionally, -m|--dry-run can be used to simulate the execution without actually performing the task actions.
Also see:
-d,--debug
Also see:
-P<property-name>=<property-value> Project Properties
See:
-D<property-name>=<property-value> System Properties
See:
-x,--exclude-task
Execute without the task following -x. For example, if I want to execute a build without tests:
gradle build -x test
or if I want to publish without running the javadoc task:
gradle build publish -x javadoc
--build-cache
--continue
Also see Ordering Tasks.
--no-daemon
See:
--stop
See:
--status
See: