[GRADLE-1346] AbstractCopyTask is UP-TO-DATE after `into` changes Created: 24/Jan/11 Updated: 23/Sep/16 Resolved: 22/Sep/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9.1 |
| Fix Version/s: | 3.2-rc-1 |
| Type: | Bug | ||
| Reporter: | Mathias Kalb | Assignee: | Lóránt Pintér |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
If you only change the "into" from a ZipTask, gradle says it is UP-TO-DATE because the "from" doesn't changed.
task zip(type: Zip) {
into('src') {
from sourceSets.all.allSource
}
from jar.outputs.files
into('libs') {
from configurations.runtime
}
}
see also http://jira.codehaus.org/browse/GRADLE-1007 |
| Comments |
| Comment by Lóránt Pintér [ 22/Sep/16 ] |
|
This has now been fixed. Copy tasks recognize changes to into. We also now track changes to sub-spec properties like caseSensitive and duplicatesStrategy etc. |
| Comment by Pepper Lebeck-Jobe [ 23/Sep/16 ] |
|
There has been a very minor (< 50ms on most builds) performance regression as a result of the fix for this issue. We have decided that we will accept this performance regression in favor of the accuracy provided by the implementation of this fix. Part of the task output cache project made it possible that CopySpec are correctly respected for up to date checking. This leads to more snapshots being created and therefore has a CPU and Memory impact but is necessary for correctness. The nightly build we used for reseting the baseline for our performance tests is just after the day the changes were (September 14th) |