[GRADLE-2913] Running a java compilation in forked mode on Windows 8 hangs. Created: 03/Oct/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
I try to solve my problem and get answer [1]http://stackoverflow.com/questions/19... 10:12:51.796 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING And nothing ever happens, process is still active. I run the same on Ubuntu - no problem, runs fine. I only have a problem on my Windows 8 machine. I found somewhere that windows have a problem with long commands, so I reduced this to only 3 or 4 java files (total command length is way below 500 chars) but it changes nothing. When I set useAnt to true - everything compiles. I also tried other command which are for sure in available - like dir or echo - effect is the same. When I insert garbage as a executable name - nothing changes. |
Comments |
Comment by Gradle Forums [ 03/Oct/13 ] |
What versions of Gradle do you observe this behavior? Cheers! |
Comment by Gradle Forums [ 03/Oct/13 ] |
C:\workspace\>gradle -v ------------------------------------------------------------ Build time: 2013-09-24 07:32:33 UTC Groovy: 1.8.6 |
Comment by Gradle Forums [ 03/Oct/13 ] |
Thanks. Can you try with Gradle 1.7? Are you using the parallel build? |
Comment by Gradle Forums [ 03/Oct/13 ] |
Im not using parallel build. |
Comment by Gradle Forums [ 03/Oct/13 ] |
Have you made sure that `javac` is on the PATH? Have you tried with the full pathname? |
Comment by Gradle Forums [ 03/Oct/13 ] |
Yes. javac is on the PATH. But I also tried with full path, tried using javac.exe instead of javac. |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |