![]() ![]() \gradle -debug > gradle-stacktrace.txtġ7:11:24.160 ġ7:11:24.161 FAILURE: Build failed with an exception.ġ7:11:24.161 ġ7:11:24.161 * What went wrong:ġ7:11:24.161 Unable to start the daemon process.ġ7:11:24.161 This problem might be caused by incorrect configuration of the daemon.ġ7:11:24.161 For example, an unrecognized jvm option is used.ġ7:11:24.162 Please refer to the user guide chapter on the daemon at ġ7:11:24.162 Please read the following process output to find out more:ġ7:11:24.162 -ġ7:11:24.162 ġ7:11:24.162 * Try:ġ7:11:24.163 Run with -stacktrace option to get the stack trace. Please read the following process output to find out more:Īt .(DaemonGreeter.java:34)Īt .(DefaultDaemonStarter.java:152)Īt .(DefaultDaemonStarter.java:135)Īt .(DefaultDaemonConnector.java:210)Īt .(DefaultDaemonConnector.java:204)Īt .(DefaultDaemonConnector.java:128)Īt .(DaemonClient.java:138)Īt .(DaemonClient.java:92)Īt .n(RunBuildAction.java:51)Īt $RunnableActionAdapter.execute(Actions.java:173)Īt .CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:291)Īt .CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:264)Īt .JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)Īt .JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)Īt .ExceptionReportingAction.execute(ExceptionReportingAction.java:33)Īt .ExceptionReportingAction.execute(ExceptionReportingAction.java:22)Īt .CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257)Īt .CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191)Īt .doAction(Main.java:33)Īt .n(EntryPoint.java:45)Īt java.base/.invoke0(Native Method)Īt java.base/.invoke(Unknown Source)Īt java.base/.invoke(Unknown Source)Īt java.base/.invoke(Unknown Source)Īt .nNoExit(ProcessBootstrap.java:60)Īt .n(ProcessBootstrap.java:37)Īt .main(GradleMain.java:23)Ĭ:\Program Files\Android\Android Studio\gradle\gradle-4.4\bin>. Please refer to the user guide chapter on the daemon at This problem might be caused by incorrect configuration of the daemon.įor example, an unrecognized jvm option is used.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |