[GRADLE-1639] CommandLineIntegrationTest fails under windows unless default user Path contains location of correct jdk Created: 24/Jun/11  Updated: 04/Jan/13  Resolved: 21/Sep/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: 1.0-milestone-5

Type: Bug
Reporter: Spencer Allain Assignee: Adam Murdoch
Resolution: Fixed Votes: 0


Running the below command results in a test failure under windows when the Path environment variable of the user does not conform to assumptions being made within ForkingGradleExecuter.java.

gradlew -DintegTest.single=CommandLineIntegrationTest :integTest:integTest

Specifically, it fails for two reasons:
[1] PATH is being set in CommandLineIntegrationTest.groovy
[2] that value is completely ignored anyway in ForkingGradleExecuter.java.

Currently ForkingGradleExecuter.java overrides the provided builder environment with System.getEnv('Path'), when instead it should attempt to utilize what is provided by the integration test itself either PATH or Path.


Comment by Luke Daley [ 30/Aug/11 ]

Adam, I think you fixed this recently.

Comment by Spencer Allain [ 21/Sep/11 ]

Just wanted to confirm that this is no longer an issue in the latest snapshot. So I recommend this issue be closed.

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