动态创建的Copy类型任务始终是UP

如果我从我的动态任务中删除类型 Copy （取消上面的行注释） ，我的任务被执行：

谢谢！

编辑：好​​的，这样任务被调用：

但它看起来我必须总是从 / 到中指定。

A 复制

doFirst 和 doLast 块会在执行过程中执行阶段，作为执行任务的一部分。两者都不能告诉任务要复制的内容： doFirst 在主任务操作（在本例中为复制）之前立即执行，但在跳过和最新检查（基于任务的配置）。 doLast 会在主要任务操作后执行，因此显然太晚了。

I've prepared a very simple script, that illustrates the problem I see using Gradle 1.7 (need to stick with it because of some plugins not yet supporting newer versions).

I'm trying to dynamically create tasks each of which corresponds to a file in the project directory. This works fine, but the tasks I create never get executed as soon as I assign them type 'Copy'.

Here is my problem build.gradle:

in this way my tasks do not get executed when I call default task calling simply gradle:

If I remove type Copy from my dynamic task (uncommenting the line above), my tasks get executed:

(You'll need to create a folder name templates in the same directory where build.gradle is located and put couple of empty files into there in order to run the test)

According to the debug output:

Skipping task ':myDist-template1' as it has no source files.

Skipping task ':myDist-template2' as it has no source files.

So how can I specify source files and make my Copy tasks execute? I've tried adding

to the task body, I've tried assigning task's inputs.source file('/my/existing/file') with no success. Could you please advise on how to modify my simple script leaving dynamic task creation and keeping my dynamic tasks of type Copy?

Thank you!

Edit: All right, this way the task gets called:

but it looks I must always specify from/into. It doesn't suffice to do that in the doLast{} body.

A Copy task only gets executed if it has something to copy. Telling it what to copy is part of configuring the task, and therefore needs to be done in the configuration phase, rather than the execution phase. These are very important concepts to understand, and you can read up on them in the Gradle User Guide or on the Gradle Forums.

doFirst and doLast blocks get executed in the execution phase, as part of executing the task. Both are too late to tell the task what to copy: doFirst gets executed immediately before the main task action (which in this case is the copying), but (shortly) after the skipped and up-to-date checks (which are based on the task's configuration). doLast gets executed after the main task action, and is therefore clearly too late.