doFirst何时在gradle中执行
为什么0000在doFirst何时在gradle中执行,gradle,Gradle,为什么0000在gradle foo之后不退出?在我删除doFirstfoo.doFirst{delete'0000'}之后,0000就在那里了 doFirst应在foo任务脚本之前执行 文件说: Task doFirst(Closure action) Adds the given closure to the beginning of this task's action list. The closure is passed this task as a parameter when e
gradle foo
之后不退出?在我删除doFirst
foo.doFirst{delete'0000'}
之后,0000就在那里了
doFirst
应在foo任务脚本之前执行
文件说:
Task doFirst(Closure action)
Adds the given closure to the beginning of this task's action list. The closure is passed this task as a parameter when executed.
完整命令日志:
isaac-mbp:swap isaac$ cat build.gradle
task foo {
mkdir '0000/a'
mkdir '0000/b'
}
foo.doFirst{ delete '0000' }
isaac-mbp:swap isaac$ gradle foo
:foo
BUILD SUCCESSFUL
Total time: 0.581 secs
isaac-mbp:swap isaac$ ls -lha 0000
ls: cannot access 0000: No such file or directory
isaac-mbp:swap isaac$ gradle -v
------------------------------------------------------------
Gradle 2.14
------------------------------------------------------------
Build time: 2016-06-14 07:16:37 UTC
Revision: cba5fea19f1e0c6a00cc904828a6ec4e11739abc
Groovy: 2.4.4
Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM: 1.8.0_25 (Oracle Corporation 25.25-b02)
OS: Mac OS X 10.11.5 x86_64
没有
build.gradle
分两个阶段运行:配置和执行mkdir
s)将在每次build.gradle
时执行,因为它是在配置时添加的:
要解决此问题,请添加操作:
task foo << {
mkdir '0000/a'
mkdir '0000/b'
}
现在,任务有两个操作:
mkdirs
s和delete
,它们将按适当的顺序执行。也请看一下非常感谢!真的节省了我几个小时的时间。接下来将了解有关gradle配置阶段的更多信息。
task foo << {
mkdir '0000/a'
mkdir '0000/b'
}
task foo << {
mkdir '0000/a'
mkdir '0000/b'
}
foo.doFirst { delete '0000' }