[GRADLE-3522] WAR task eagerly triggers dependency resolution Created: 16/Aug/16  Updated: 16/Aug/16  Resolved: 16/Aug/16

Status: Resolved
Project: Gradle
Affects Version/s: 3.0
Fix Version/s: 3.1-rc-1

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Mark Vieira (Inactive)
Resolution: Fixed Votes: 0


This issue was originally reported on the forums:


This looks to be a side effect from the Groovy to Java conversions. What was done is that the War task copy specs are being build from Iterable<File> rather than a FileCollection. The result is that when we traverse the task dependency graph we trigger dependency resolution in order to retrieve the Iterable<File> rather than relying on the laziness of FileCollection.


Generated at Wed Jun 30 12:51:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.