Gradle Goodness: Check Task Dependencies With a Dry Run
We can run a Gradle build without any of the task actions being executed. This is a so-called dry run of our build. We can use the dry run of a build to see if the task dependencies we have defined or are defined in a plugin are defined properly. Because all tasks and task dependencies are resolved if we use the dry run mode we can see in the output which tasks are executed.
We define a simple build file with three tasks and some task dependencies:
0.
def
printTaskNameAction = {
1.
println
"Running ${it.name}"
2.
}
3.
4.
task first << printTaskNameAction
5.
6.
task second(dependsOn: first) << printTaskNameAction
7.
8.
task third(dependsOn: [first, second]) << printTaskNameAction
To run a Gradle build as a dry run we can use the command line option -m
or --dry-run
. So let's execute the task third
with the dry run command line option:
$ gradle -m third
:first SKIPPED
:second SKIPPED
:third SKIPPED
BUILD SUCCESSFUL
Total time: 2.242 secs
$
And we see in the output none of the tasks are really executed, because SKIPPED
is shown, but we do see the task names of the tasks that are resolved.
Written with Gradle 2.2.
最新文章
- 航旅事业群面试(li)
- 网站跨站点脚本,Sql注入等攻击的处理
- [原创]在Linux系统Ubuntu14.04上安装部署docker。
- ASP.NET应用中会话状态丢失及解决策略
- Android_按两次返回键退出程序和长按返回键退出程序
- lintcode:二叉树的中序遍历
- Oracle 动态视图1 V$LOCK
- jsp中<;c:if>;与<;s:if>;的区别
- 【spring-boot】spring aop 面向切面编程初接触--切点表达式
- Python开发【第八篇】:网络编程
- Axure自动备份功能!让意外不在可怕!
- UML简单梳理类图
- PHP常用函数(一):数组常用函数
- webstorm破解版
- 转:Delta3D Editor编译成功
- [javaSE] 集合框架(共性方法)
- ---web模型 --mvc和模型--struts2 入门
- C# Winform backgroundWorker组件使用
- 简单实现MemCachedUtil
- 【转】获取Windows系统明文密码神器