Open wscalf opened 9 years ago
The only thing I notice is that your username has spaces and it forces the javac command line to use quotes for the classpath parameter. That seems to cause some trouble to javac. @sharwell, do you think this is something that can be fixed in the javac task?
I just tested a build with spaces (Console Application project) and it worked fine. Is there another project type that's currently failing for this?
I think the problem is specifically in the class path parameter for javac.exe. It seems to be specific to Gradle projects that cache all their dependencies in the path
All right, as a workaround I created a new user with no spaces, and that seemed to get me past that issue and on to the one reported #11. After running the pre-provision command from there I'm up and running!
..My game is crawling, but I think that's more an artifact of virtualization than anything. I'll try setting up a dev workspace on a physical box.
Thanks a bunch!
Same issue here, except I'm using a single user version of window, so no workaround.
I saw a few of these in the closed session, but I don't think any of them were the same issue I'm having, and those solutions don't appear to have worked.
So, initially, I wasn't getting very far (and was getting the same error as #9. ) This turned out to be because I hadn't installed JDK at all. Oops.
Now it goes all the way through creating the workspace...and javac crashes when compiling the code with exit code 2. I turned up the build output and found that it was complaining about its command-line arguments, which appear to be a semicolon-delimited list of files (the actual error is: invalid flag: ; )
I'm..not sure what to do with that. Just to be safe, I checked my JAVA_HOME environment variable and I don't appear to have one. I tried adding one that points to where the JDK is installed (C:\Program Files\Java\jdk1.8.0_45) and had no perceivable change in results.
Here's my build output (set to Diagnostic):