java中gradlew 命令_gradle命令学习
概述
命令學習比較枯燥，全部是例子~
gradle版本
假設你的本地gradle已經安裝配置完成。沒有安裝配置的，可以參考 gradle安裝
C:\Users\yueling.DANGDANG>gradle -v
------------------------------------------------------------
Gradle 4.5.1
------------------------------------------------------------
Build time: 2018-02-05 13:22:49 UTC
Revision: 37007e1c012001ff09973e0bd095139239ecd3b3
Groovy: 2.4.12
Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017
JVM: 1.8.0_73 (Oracle Corporation 25.73-b02)
OS: Windows 7 6.1 amd64C:\Users\yueling.DANGDANG>
語法
gradle [taskName...][--option-name...]
gradlew是包裝器，自動下載包裝里定義好的gradle 版本，保證編譯環境統一，gradle 是用本地的gradle。所以./gradlew、gradle通用，不神秘，使用更方便一些,可以使用gradle互相替換。其中gradlew的內容可以在項目的目錄下查看。
任務
如果需要處理多任務，任務列表必須使用空格分割開，如
gradle test deploy
選項
選項可以放在任務列表前也可以放在任務列表后，如下的寫法作用是相同的
gradle --console=plain test
gradle test --console=plain
記憶技巧：長格式的選項 表示啟用特性的都具有反向操作(關閉特性)，關閉特性長選項格式在啟用特性前綴no-
--build-cache--configure-on-demand--daemon--parallel--scan
--no-build-cache--no-configure-on-demand--no-daemon--no-parallel--no-scan
命令列表
打開控制臺，
command_Parameters
introduction
-?, -h, –help
展示幫助信息
-a, –no-rebuild
忽略構建”項目依賴”,[廢棄]
-b, –build-file
使用用-b參數將會忽略setting文件,用指定的.gradle文件進行構建(默認情況下首先會尋找當前目錄下的 build.gradle文件或依據settings.gradle中的配置尋找子項目中的build.gradle)
–build-cache
支持gradle緩存。Gradle將試圖重用以前的版本的輸出
-c, –settings-file
執行指定的*.gralde文件(默認settings.gradle)
–configure-on-demand
配置必要的項目。Gradle將試圖減少大型多項目構建的配置時間
–console
指定控制臺輸出類型,可選值有’plain’、’auto’(默認)、’rich’、’verbose’。plain 是生成普通的文本，該選項禁止所有顏色和富文本輸出;auto當構建程序與控制臺相關聯時啟動顏色和富文本輸出，或者不關聯時生成普通文本;rich 啟動顏色和富文本輸出，忽略構建程序是否關聯了控制臺,如果沒有關聯構建輸出將輸出 ANSI 控制字符來生產富文本輸出;verbose會輸出更多的詳細信息(感覺很亂，調試問題可能會用到)
–continue
構建時遇到錯誤忽略報錯,繼續構建,默認報錯后終止構建
-D, –system-prop
-D屬性會被傳送給啟動Gradle的jvm，作為一個系統屬性被jvm使用(例如:-Dmyprop=myvalue)
-d, –debug
指定日志輸出級別為debug,可打印一般堆棧信息
–daemon
使用Gradle守護進程執行構建,如果沒有守護進程則啟動一個守護進程
–foreground
以foreground形式啟動守護進程
-g, –gradle-user-home
指定默認的指定Gradle 用戶home目錄.默認在”用戶目錄/.gradle”
-I, –init-script
運行指定初始化腳本,腳本會在build之前執行.查找init.gradle的路徑順序：./,USER_HOME/.gradle/ ,USER_HOME/.gradle/init.d/,GRADLE_HOME/init.d/
-i, –info
指定日志級別為info
–include-build
在組合中包含指定的構建
-m, –dry-run
模擬任務執行過程并將過程打印出來,并非真正執行,目的是展示執行的過程
–max-workers
設定參與構建的cpu的核數
–no-build-cache
禁用構建緩存
–no-configure-on-demand
根據需要禁用配置
–no-daemon
禁用守護進程,不使用守護進程執行構建. 如果你已經配置了Gradle總會使用守護進程運行，此選項有幫助
–no-parallel
禁止使用并行模式構建項目
–offline
采用離線模式構建項目,不使用網路資源(此時很有可能出現構建失敗的情況慎用)
-P, –project-prop
設置Gradle的項目參數,會被直接加載到Gradle領域對象上(例如:-Pmyprop=myvalue)
-p, –project-dir
為gradle指定起始目錄。默認為當前目錄
–parallel
采用并行模式構建。gradle采用配置的線程數進行構建
–profile
存儲一份執行報告到/reports/profile,包括總時間和在配置和任務執行階段的細節。并以時間大小倒序排列，并且記錄了任務的執行情況.Gradle會根據構建時間命名這些報告文件
–project-cache-dir
指定項目的緩存目錄。默認在項目目錄中。
-q, –quiet
靜默方式，只輸出error信息
–recompile-scripts
強制構建腳本重新編譯[廢棄]
–refresh-dependencies
刷新依賴的狀態
–rerun-tasks
忽略先前緩存的任務結果
-S, –full-stacktrace
打印全部詳細信息，所有異常的堆棧信息
-s, –stacktrace
打印所有異常的堆棧信息
–scan
創建一個構建掃描。如果構建掃描插件沒有被應用，那么gradle會發出警告(https://gradle.com/build-scans)
–status
統計信息，展示正在運行和最近停止的gradle進程
–stop
如果守護進程正在運行，停止gradle的守護進程
-t, –continuous
連續構建模式,采用此模式后會監聽所有構建文件變化,文件發生變化后會自動重新構建
-u, –no-search-upward
不使用父目錄中的settings.gradle文件,如果不添加此項,父目錄的setting.gradle會覆蓋子目錄下的配置
-v, –version
打印gradle版本信息
-w, –warn
指定日志級別為warn
–warning-mode
指定要生成的警告模式。值是’all’, ‘summary’(默認) or ‘no’
-x, –exclude-task
任務排除,跳過執行指定任務
命令的一些用法
準備一個項目
使用eclipse創建一個gradle的項目:gradleDemo
該項目不寫任何代碼，只配置build.gradle,只為了演示命令的基本用法及效果
build.gradle
apply plugin: 'java-library'
// In this section you declare where to find the dependencies of your project
repositories {
// Use jcenter for resolving your dependencies.
// You can declare any Maven/Ivy/file repository here.
jcenter()
}
dependencies {
// This dependency is exported to consumers, that is to say found on their compile classpath.
api 'org.apache.commons:commons-math3:3.6.1'
// This dependency is used internally, and not exposed to consumers on their own compile classpath.
implementation 'com.google.guava:guava:23.0'
// Use JUnit test framework
testImplementation 'junit:junit:4.12'
}
//有依賴
task base {
doLast {
println "i'm base!"
}
}
task extend(dependsOn: base) {
doLast {
println "I'm extend!"
}
}
//使用<
task dolast <
println "show me! dolast"
println ("show me! dolast")
println ("show me! dolast");
}
//多字節名稱使用間歇eEE
task extendExpExp() {
doLast {
println "I'm extendExpExp"
}
}
實驗
挑一些常用的命令用實例說明用法,首先切換到項目所在目錄
Microsoft Windows [版本 6.1.7601]
版權所有 (c) 2009 Microsoft Corporation。保留所有權利。
C:\Users\yueling.DANGDANG>cd /d d:\eclipsWS\gradleWS\gradleDemo
d:\eclipsWS\gradleWS\gradleDemo>
直接執行命令
d:\eclipsWS\gradleWS\gradleDemo>gradle
:help
Welcome to Gradle 4.5.1.
To run a build, run gradle ...
To see a list of available tasks, run gradle tasks
To see a list of command-line options, run gradle --help
To see more detail about a task, run gradle help --task
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
執行任務和任務的所有依賴
d:\eclipsWS\gradleWS\gradleDemo>gradle extend
:base
i'm base!
:extend
I'm extend!
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
2 actionable tasks: 2 executed
多模塊項目中，可以在root項目中指定項目名稱來執行,此項目時單模塊的，不在此演示,格式為 gradle projectName:taskName
多任務執行
d:\eclipsWS\gradleWS\gradleDemo>gradle base dolast
:base
i'm base!
:dolast
show me! dolast
show me! dolast
show me! dolast
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
2 actionable tasks: 2 executed
排除模塊執行
d:\eclipsWS\gradleWS\gradleDemo>gradle base dolast -x dolast
:base
i'm base!
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed>
強制執行任務
d:\eclipsWS\gradleWS\gradleDemo>gradle base --rerun-tasks
:base
i'm base!
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
遇到錯誤繼續執行
d:\eclipsWS\gradleWS\gradleDemo>gradle base --continue
:base
i'm base!
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed
當然目前該項目沒有錯誤^_^
task控制 doFirst 和doLast
在這里我們使用它來控制一些輸出作為演示(實際項目中可以填入更復雜的actions)，前面的例子中已經使用了，還可以更靈活第控制,如在build.gradle中配置添加
base.doLast {
println "addtion end......"
}
base.doFirst {
println "addtion start......"
}
那么輸入就會改變，在任務開始和結束打印的內容隨之變化
d:\eclipsWS\gradleWS\gradleDemo>gradle base
:base
addtion start......
i'm base!
addtion end......
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
靜默構建
多余的日志信息不見了~~~
d:\eclipsWS\gradleWS\gradleDemo>gradle -q base
addtion start......
i'm base!
addtion end......
d:\eclipsWS\gradleWS\gradleDemo>
設置日志級別
分別演示了設置成warn和info的情況
d:\eclipsWS\gradleWS\gradleDemo>gradle -w base
addtion start......
i'm base!
addtion end......
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
d:\eclipsWS\gradleWS\gradleDemo>gradle -i base
Initialized native services in: C:\Users\yueling.DANGDANG\.gradle\native
The client will now receive all logging from the daemon (pid: 59652). The daemon log file: C:\Users\yueling.DANGDANG\.gradle\daemon\4.5.1\daemon-59652.out.log
Starting 33rd build in daemon [uptime: 3 hrs 53 mins 31.583 secs, performance: 100%, no major garbage collections]
Using 4 worker leases.
Starting Build
Settings evaluated using settings file 'D:\eclipsWS\gradleWS\gradleDemo\settings.gradle'.
Projects loaded. Root project using build file 'D:\eclipsWS\gradleWS\gradleDemo\build.gradle'.
Included projects: [root project 'gradleDemo']
Evaluating root project 'gradleDemo' using build file 'D:\eclipsWS\gradleWS\gradleDemo\build.gradle'.
All projects evaluated.
Selected primary task 'base' from project :
Tasks to be executed: [task ':base']
:base (Thread[Daemon worker Thread 17,5,main]) started.
:base
Task ':base' is not up-to-date because:
Task has not declared any outputs.
addtion start......
i'm base!
addtion end......
:base (Thread[Daemon worker Thread 17,5,main]) completed. Took 0.0 secs.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
VCS Checkout Cache (D:\eclipsWS\gradleWS\gradleDemo\.gradle\vcsWorkingDirs) has not been cleaned up in 0 days
控制臺輸出類型
可以指定的類型有：’plain’、’auto’(默認)、’rich’、’verbose’
d:\eclipsWS\gradleWS\gradleDemo>gradle base --console plain
:base
addtion start......
i'm base!
addtion end......
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed
d:\eclipsWS\gradleWS\gradleDemo>gradle base --console rich
[1A[1m 0% CONFIGURING [0s][m[35D[1B[1A[0K
[1m> Task :base[m[33m [39m
addtion start......
i'm base!
addtion end......
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
[32;1mBUILD SUCCESSFUL[0;39m in 0s
1 actionable task: 1 executed
windows下顯示有點問題，不支持顏色的控制~尊駕可以移步到linux下執行，顏色等都顯示出來了
status
d:\eclipsWS\gradleWS\gradleDemo>gradle base --status
PID STATUS INFO
59652 IDLE 4.5.1
Only Daemons for the current Gradle version are displayed. See https://docs.gradle.org/4.5.1/userguide/gradle_daemon.html#sec:status
scan
這個過程是需要交互的，同意即可，即輸入yes；然后按提供的地址打開url，提供郵件地址；按郵件里的提示查看報告
d:\eclipsWS\gradleWS\gradleDemo>gradle base --scan
:base
addtion start......
i'm base!
addtion end......
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 2s
1 actionable task: 1 executed
Publishing a build scan to scans.gradle.com requires accepting the Terms of Service defined at https://scans.gradle.com/terms-of-service. Do you accept these terms? [yes, no]
yes
Gradle Cloud Services license agreement accepted.
Publishing build scan...
https://gradle.com/s/pmnnhqgqmv4zw
更換setting.gradle配置文件
將一份配置文件復制到項目外(本例直接復制到d盤),修改其中的項目名稱為gradleDemooooooooooooo
rootProject.name = 'gradleDemooooooooooooo'
d:\eclipsWS\gradleWS\gradleDemo>gradle base -c d:\settings.gradle -i
Initialized native services in: C:\Users\yueling.DANGDANG\.gradle\native
The client will now receive all logging from the daemon (pid: 59652). The daemon log file: C:\Users\yueling.DANGDANG\.gradle\daemon\4.5.1\daemon-59652.out.log
Starting 45th build in daemon [uptime: 4 hrs 20 mins 27.835 secs, performance: 100%, no major garbage collections]
Using 4 worker leases.
Starting Build
Settings evaluated using settings file 'D:\settings.gradle'.
Projects loaded. Root project using build file 'D:\build.gradle'.
Included projects: [root project 'gradleDemooooooooooooo']
Evaluating root project 'gradleDemooooooooooooo' using build file 'D:\build.gradle'.
All projects evaluated.
Selected primary task 'base' from project :
Tasks to be executed: [task ':base']
:base (Thread[Task worker for ':',5,main]) started.
:base
Task ':base' is not up-to-date because:
Task has not declared any outputs.
addtion start......
i'm base!
addtion end......
:base (Thread[Task worker for ':',5,main]) completed. Took 0.001 secs.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
VCS Checkout Cache (D:\.gradle\vcsWorkingDirs) has not been cleaned up in 0 days
更換build.gradle配置文件
復制一份配置文件到D盤，并添加任務
task baseadd {
doLast {
println "build.gradle not in dir!"
}
}
d:\eclipsWS\gradleWS\gradleDemo>gradle baseadd -b d:\build.gradle
:baseadd
build.gradle not in dir!
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed
gradle build
裝配所有輸出并運行所有檢查
d:\eclipsWS\gradleWS\gradleDemo>gradle build
:compileJava
:processResources NO-SOURCE
:classes
:jar
:assemble
:compileTestJava
:processTestResources NO-SOURCE
:testClasses
:test
:check
:build
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 18s
4 actionable tasks: 4 executed
gradle run
運行所有任務
gradle check
驗證任務，包括測試和初始化
d:\eclipsWS\gradleWS\gradleDemo>gradle check
:compileJava
:processResources NO-SOURCE
:classes
:compileTestJava
:processTestResources NO-SOURCE
:testClasses
:test
:check
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 2s
3 actionable tasks: 3 executed
gradle clean
清理所有輸出
d:\eclipsWS\gradleWS\gradleDemo>gradle clean
:clean
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed
gradle projects
項目報告,包括子項目
d:\eclipsWS\gradleWS\gradleDemo>gradle projects
:projects
------------------------------------------------------------
Root project
------------------------------------------------------------
Root project 'gradleDemo'
No sub-projects
To see a list of the tasks of a project, run gradle :tasks
For example, try running gradle :tasks
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 0s
1 actionable task: 1 executed
gradle tasks
所有的tasks列表
d:\eclipsWS\gradleWS\gradleDemo>gradle tasks
:tasks
------------------------------------------------------------
All tasks runnable from root project
------------------------------------------------------------
Build tasks
-----------
assemble - Assembles the outputs of this project.
build - Assembles and tests this project.
buildDependents - Assembles and tests this project and all projects that depend on it.
buildNeeded - Assembles and tests this project and all projects it depends on.
classes - Assembles main classes.
clean - Deletes the build directory.
jar - Assembles a jar archive containing the main classes.
testClasses - Assembles test classes.
Build Setup tasks
-----------------
init - Initializes a new Gradle build.
wrapper - Generates Gradle wrapper files.
Documentation tasks
-------------------
javadoc - Generates Javadoc API documentation for the main source code.
Help tasks
----------
buildEnvironment - Displays all buildscript dependencies declared in root project 'gradleDemo'.
components - Displays the components produced by root project 'gradleDemo'. [incubating]
dependencies - Displays all dependencies declared in root project 'gradleDemo'.
dependencyInsight - Displays the insight into a specific dependency in root project 'gradleDemo'.
dependentComponents - Displays the dependent components of components in root project 'gradleDemo'. [incubating]
help - Displays a help message.
model - Displays the configuration model of root project 'gradleDemo'. [incubating]
projects - Displays the sub-projects of root project 'gradleDemo'.
properties - Displays the properties of root project 'gradleDemo'.
tasks - Displays the tasks runnable from root project 'gradleDemo'.
Verification tasks
------------------
check - Runs all checks.
test - Runs the unit tests.
Rules
-----
Pattern: clean: Cleans the output files of a task.
Pattern: build: Assembles the artifacts of a configuration.
Pattern: upload: Assembles and uploads the artifacts belonging to a configuration.
To see all tasks and more detail, run gradle tasks --all
To see more detail about a task, run gradle help --task
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s
1 actionable task: 1 executed
gradle tasks –all
gradle -q help –task base
展示指定任務的詳細信息
d:\eclipsWS\gradleWS\gradleDemo>gradle -q help --task base
Detailed task information for base
Path
:base
Type
Task (org.gradle.api.Task)
Description
-
Group
-
gradle dependencies
展示項目依賴
d:\eclipsWS\gradleWS\gradleDemo>gradle dependencies
:dependencies
------------------------------------------------------------
Root project
------------------------------------------------------------
api - API dependencies for source set 'main'. (n)
\--- org.apache.commons:commons-math3:3.6.1 (n)
apiElements - API elements for main. (n)
No dependencies
archives - Configuration for archive artifacts.
No dependencies
compile - Dependencies for source set 'main' (deprecated, use 'implementation ' instead).
No dependencies
compileClasspath - Compile classpath for source set 'main'.
+--- org.apache.commons:commons-math3:3.6.1
\--- com.google.guava:guava:23.0
+--- com.google.code.findbugs:jsr305:1.3.9
+--- com.google.errorprone:error_prone_annotations:2.0.18
+--- com.google.j2objc:j2objc-annotations:1.1
\--- org.codehaus.mojo:animal-sniffer-annotations:1.14
compileOnly - Compile only dependencies for source set 'main'.
No dependencies
……
gradle buildEnvironment
展示構建環境依賴關系報告
gradle dependencyInsight
展示依賴關系報告
gradle model
展示模型關系報告
d:\eclipsWS\gradleWS\gradleDemo>gradle model
:model
------------------------------------------------------------
Root project
------------------------------------------------------------
+ binaries
| Type: org.gradle.platform.base.BinaryContainer
| Creator: BinaryBasePlugin.Rules#binaries(BinaryContainer)
| Rules:
? JavaBasePlugin.Rules#attachBridgedBinaries(BinaryContainer, JavaBasePlugin.BridgedBinaries)
+ main
| Type: org.gradle.api.internal.jvm.DefaultClassDirectoryBinarySpec_Decorated
| Value: Classes 'main'
| Creator: JavaBasePlugin.Rules#attachBridgedBinaries(BinaryContainer, JavaBasePlugin.BridgedBinaries) > put()
| Rules:
? BinaryBasePlugin.Rules#defineBuildLifecycleTask(BinarySpecInternal, ITaskFactory)
? BinaryBasePlugin.Rules#addSourceSetsOwnedByBinariesToTheirInputs(BinarySpecInternal)
+ test
| Type: org.gradle.api.internal.jvm.DefaultClassDirectoryBinarySpec_Decorated
| Value: Classes 'test'
| Creator: JavaBasePlugin.Rules#attachBridgedBinaries(BinaryContainer, JavaBasePlugin.BridgedBinaries) > put()
| Rules:
? BinaryBasePlugin.Rules#defineBuildLifecycleTask(BinarySpecInternal, ITaskFactory)
? BinaryBasePlugin.Rules#addSourceSetsOwnedByBinariesToTheirInputs(BinarySpecInternal)
+ components
| Type: org.gradle.platform.base.ComponentSpecContainer
| Creator: ComponentBasePlugin.PluginRules#components(ComponentSpecContainer)
……
還有一些沒有演示的命令，根據幫助文檔都能嘗試一下
總結
以上是生活随笔為你收集整理的java中gradlew 命令_gradle命令学习的全部內容，希望文章能夠幫你解決所遇到的問題。
- 上一篇： mysql产品优化方案_mysql的优化
- 下一篇： c99什么意思_C语言中-是什么意思啊？