摘要:注有關(guān)詳細(xì)信息請使用重新編譯。個(gè)錯(cuò)誤原來是的找不到了徹底解決了可以在右側(cè)找到對應(yīng)的各種快捷鍵
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ":app:compileDebugJavaWithJavac". at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626) at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.lang.Thread.run(Thread.java:745)
在AndroidStudio(mac os)的terminal中輸入命令
./gradlew compileDebug --stacktrace
windows下輸入
gradlew compileDebug --stacktrace
查看日志
* What went wrong: Task "compileDebug" is ambiguous in root project "DefineViewStudy". Candidates are: "compileDebugAidl", "compileDebugAndroidTestAidl", "compileDebugAndroidTestJavaWithJavac", "compileDebugAndroidTestNdk", "compileDebugAndroidTestRenderscript", "compileDebugAndroidTestShaders", "compileDebugAndroidTestSources", "compileDebugJavaWithJavac", "compileDebugNdk", "compileDebugRenderscript", "compileDebugShaders", "compileDebugSources", "compileDebugUnitTestJavaWithJavac", "compileDebugUnitTestSources". * Try: Run gradlew tasks to get a list of available tasks. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Exception is: org.gradle.execution.TaskSelectionException: Task "compileDebug" is ambiguous in root project "DefineViewStudy". Candidates are: "compileDebugAidl", "compileDebugAndroidTestAidl", "compileDebugAndroidTestJavaWithJavac", "compileDebugAndroidTestNdk", "compileDebugAndroidTestRenderscript", "compileDebugAndroidTestShaders", "compileDebugAndroidTestSources", "compileDebugJavaWithJavac", "compileDebugNdk", "compileDebugRenderscript", "compileDebugShaders", "compileDebugSources", "compileDebugUnitTestJavaWithJavac", "compileDebugUnitTestSources".
注意到這句話Task "compileDebug" is ambiguous in root project "DefineViewStudy". 單詞
ambiguous是模糊不清的意思.嘗試著把命令改為
./gradlew compileDebugJavaWithJavac
windows下輸入
gradlew compileDebugJavaWithJavac
這次打印的信息很明了了.
/Users/xxx/work/workspace/github/DefineViewStudy/app/src/main/java/com/idealcn/define/view/ui/MainFragment.java:70: 錯(cuò)誤: 找不到符號 case R.id.round_cake: ^ 符號: 變量 round_cake 位置: 類 id /Users/guoning/work/workspace/github/DefineViewStudy/app/src/main/java/com/idealcn/define/view/ui/MainFragment.java:74: 錯(cuò)誤: 找不到符號 case R.id.drag: ^ 符號: 變量 drag 位置: 類 id 注: 某些輸入文件使用或覆蓋了已過時(shí)的 API。 注: 有關(guān)詳細(xì)信息, 請使用 -Xlint:deprecation 重新編譯。 2 個(gè)錯(cuò)誤
原來是view的id找不到了.徹底解決了!
可以在Android-studio右側(cè)找到gradlew對應(yīng)的各種快捷鍵
文章版權(quán)歸作者所有,未經(jīng)允許請勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請注明本文地址:http://specialneedsforspecialkids.com/yun/68968.html
摘要:項(xiàng)目打包運(yùn)行命令的時(shí)候報(bào)錯(cuò)報(bào)錯(cuò)詳情如下解決辦法已經(jīng)執(zhí)行過命令添加了平臺,直接打開目錄你的項(xiàng)目工程文件中找到方法在這個(gè)方法之前添加上如下內(nèi)容原因分析帶號是指要用最新版本。 ionic項(xiàng)目打包運(yùn)行命令 ionic build android的時(shí)候報(bào)錯(cuò) 報(bào)錯(cuò)詳情如下 :processDebugResourcesERROR: In FontFamilyFont, unable to find...
摘要:添加插件可能會(huì)遇到如下報(bào)錯(cuò)提示信息如果你在時(shí),有注意到是需要版本大于等于解決方案所以只需要運(yùn)行命令這樣就在運(yùn)行就能打包成功了 添加ionic插件cordova-plugin-file可能會(huì)遇到如下報(bào)錯(cuò) 提示信息 :processDebugResources :generateDebugSources :compileDebugJava apache/cordova/filetransf...
摘要:添加插件可能會(huì)遇到如下報(bào)錯(cuò)提示信息如果你在時(shí),有注意到是需要版本大于等于解決方案所以只需要運(yùn)行命令這樣就在運(yùn)行就能打包成功了 添加ionic插件cordova-plugin-file可能會(huì)遇到如下報(bào)錯(cuò) 提示信息 :processDebugResources :generateDebugSources :compileDebugJava apache/cordova/filetransf...
閱讀 1996·2021-09-30 09:53
閱讀 1840·2021-09-24 09:48
閱讀 1755·2019-08-30 14:01
閱讀 2170·2019-08-29 18:35
閱讀 1249·2019-08-26 18:27
閱讀 2978·2019-08-26 12:12
閱讀 941·2019-08-23 17:16
閱讀 931·2019-08-23 15:31