[GRADLE-536] integTest target in Gradle's own build can't be re-run without clean Created: 30/Jun/09  Updated: 04/Jan/13  Resolved: 01/Jul/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.6
Fix Version/s: 0.7

Type: Bug
Reporter: Steve Appling Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Attachments: Text File integTest.patch    


You can't re-run the integTest target in gradle's build without cleaning it each time. It takes a really long time to run now, so this is a pain.

There are two problems with this that I saw:

  • The integTest.doFirst closure that copies over the explodedDist lib directory doesn't delete the old gradle*.jar files first, so you get duplicates.
  • The SamplesJavaMultiProjectIntegrationTest does not properly clean itself up, so it can't be re-run. It attempts to clean up in its setup method, but has a bug and specifies the wrong directories to delete.

This patch should correct both of these issues.

Comment by Adam Murdoch [ 01/Jul/09 ]

Thanks for the patch. I've applied it, with one small modification, so that integTest works after a clean as well.

Generated at Wed Jun 30 11:32:36 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.