This still affects 2.2.
AbstractFileTreeElement.copyTo(File) could be extended by target.setLastModified(getLastModified());, but that would make it the default behavior. I'm not sure if that's a good idea.

Based on Jochen's comment I did the following workaround.
It records all the FileCopyDetails in a list and applies the dates in doLast. (target files have not been created at execution time of eachFile closure.)

task extractSomeStuff(type: Copy) {
	from zipTree(tasks.createSomeStuff.archivePath)
	destinationDir temporaryDir
	def copyDetails = []
	eachFile { copyDetails << it }
	doLast {
		copyDetails.each { FileCopyDetails details ->
			def target = new File(destinationDir, details.path)
			if(target.exists()) {
				target.setLastModified(details.lastModified)
			}
		}
	}
}

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

This issue affects Gradle 3.2. I can create a sample Gradle build if you like, but I think the issue should be clear without it.

@Jochen Could you please provide an reproducible example and add it to a new issue on GitHub?

https://github.com/gradle/gradle/issues/1252.

Thanks, @Jochen.