[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


I try to solve my problem and get answer [1]http://stackoverflow.com/questions/19...
When I run compilation with forked mode it hangs - I mean the debug output is like

10:12:51.796 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
10:12:51.797 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'javac'.
10:12:51.821 [INFO] [org.gradle.process.internal.ProcessParentingInitializer] An attempt to initialize for well behaving parent process finished.

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.
I tried running gradle command as admin - no change.
[1] http://stackoverflow.com/questions/19124873/sun-jpegimageencoder-compilation-in-gradle

Comment by Gradle Forums [ 03/Oct/13 ]

What versions of Gradle do you observe this behavior?


Comment by Gradle Forums [ 03/Oct/13 ]

C:\workspace\>gradle -v

Gradle 1.8

Build time: 2013-09-24 07:32:33 UTC
Build number: none
Revision: 7970ec3503b4f5767ee1c1c69f8b4186c4763e3d

Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.2 compiled on July 8 2013
Ivy: 2.2.0
JVM: 1.7.0_25 (Oracle Corporation 23.25-b01)
OS: Windows 8 6.2 amd64

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.
I first run it on gradle 1.6 (the one I had already installed), then switched to newest 1.8.
I also run it on 1.7 - it behaves exactly the same.

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.
I also moved my JDK to C:\ to avoid spaces in the name. Nothing changed

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:

  • 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!

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.

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