[GRADLE-764] Fix Gradle's developer build on windows Created: 02/Dec/09  Updated: 04/Jan/13  Resolved: 04/Aug/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Fixed Votes: 0


Currently, some integration tests fail on windows, when they are run in non-forking mode. A work-around is to run gradle clean check integTest.

Comment by Hans Dockter [ 11/Dec/09 ]

This is fixed, isn't it?

Comment by Adam Murdoch [ 25/Feb/10 ]

Currently, there are 2 problems with non-forking integration tests on windows:

  • The Ant junitreport task does not close the junit report index.html file, which locks it and prevents later int tests from performing a clean for the given project. Might be fixed in Ant 1.8.0.
  • The build ClassLoader does not close the buildSrc jar at the end of a build, which locks it and prevents an int test from testing that the jar is rebuilt when the buildSrc src changes.
Comment by Luke Daley [ 30/Aug/11 ]

Is this still an issue?

Comment by Simon Epstein [ 16/Nov/11 ]

I just ran gradlew developerBuild successfully on Windows XP:

D:\gradle>gradlew --version

Gradle 1.0-milestone-6-20111113105934+0100

Gradle build time: Sunday, 13 November 2011 09:59:34 o'clock UTC
Groovy: 1.8.4
Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ivy: 2.2.0
JVM: 1.6.0_29 (Sun Microsystems Inc. 20.4-b02)
OS: Windows XP 5.1 x86

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