Ge=en, -Duser.variant, -cp, C:\Program Files\Android\Android Studio\gradle\gradle-2.14.1\lib\gradle-launcher-2.14.1.jar]Ģ1:22:06.011 Starting daemon process: workingDir = C:\Users\adle\daemon\2.14.1, daemonArgs: [C:\Program Files\Java\jdk1.8.0_111\bin\java.exe, -Xmx15ģ6m, -Dfile.encoding=windows-1252, untry=US, -Duser.language=en, -Duser.variant, -cp, C:\Program Files\Android\Android Studio\gradle\gradle-2.14.1\lib\gradle-launcher-2.14.1.jar, .bootsĢ1:22:06.027 Starting process ‘Gradle build daemon’. Please consider using the daemon: Ģ1:22:06.011 Using daemon args: [C:\Program Files\Java\jdk1.8.0_111\bin\java.exe, -Xmx1536m, -Dfile.encoding=windows-1252, untry=US, -Duser.langua Continuing with fallback.Ģ1:21:57.073 Using JDK 7 file service .7SymlinkĢ1:22:05.996 To honour the JVM settings for this build a new JVM will be forked. init -debugĢ1:21:56.995 Native-platform posix files is not available. From the gradle init -debug output:Ĭ:\Users\Dada\AndroidStudioProjects\MyApplication\gradle\wrapper>“java.exe” “=gradle” -classpath "c:\Program Files\Android\Android Studio\gradle\gradle-2.14.1\bin…\lib\gradle-launcher-2.14.1.jar" I find that a simple gradle init fails because a connection to the daemon cannot be completed on the loopback address.
I have tried simply running Gradle from a command prompt and have not been able to get it to work. I’m at home so there is no proxy server and I am using 2.2.3, not 1.x (and JDK 7 is no longer supported) so none of the solutions work for me.
I Googled for that and found most reports were due to needing proxy settings corrected or with Android Studio 1.x and not using JDK 8. Most likely the proess died immediately after connection. Gradle ‘MyApplication’ project refresh failedĮrror: The first result from the daemon was empty. As soon as I finish with the new project wizard I see the Gradle Build message for a long while then I see: I just installed Android Studio 2.2.3 on my desktop but cannot get it to build even an “Empty” new project.
0 kommentar(er)
