[Android fix] java.exe finished with non-zero exit value 2

最新推荐文章于 2022-06-03 16:34:08 发布

原创最新推荐文章于 2022-06-03 16:34:08 发布 · 675 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#android

工具效率专栏收录该内容

11 篇文章

订阅专栏

遇到Android项目中执行任务失败的错误时，通过检查重复依赖、删除本地包及调整build.gradle依赖关系解决了问题。重点是清理项目依赖并确认正确的依赖引入方式。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Process ”C:\Program Files\Java\jdk1.8.0_60\bin\java.exe” finished with non-zero exit value 2

在StackOverflow上查到的：http://stackoverflow.com/questions/32392245/execution-failed-for-task-splashdexdebug

按照提示，尝试了project的module setting
（传图失败orz）

删除重复的依赖包，另外还有project的build.gradle的dependence里的包、项目依赖关系；

认真找吧。

PS：我的是support-v4 有本地包，也添加了lib引用；去除本地包，问题解决

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

微信公众号_程序之炼

关注关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

【OpenHarmony4.1 之 U-Boot 2024.07源码深度解析】006 - Makefile 编译脚本逐行深度解析

|~~~热爱生活、努力学习的小伙汁~~~|

06-15

1168

【OpenHarmony4.1 之 U-Boot 2024.07源码深度解析】006 - Makefile 编译脚本逐行深度解析

迁移到AndroidX-你遇到的和即将遇到的，这里都有

micotale的博客

07-26

1万+

一. 第一次迁移 1.背景： AndroidX 会将原始支持库 API 软件包映射到androidx命名空间。只有软件包和 Maven 工件名称发生了变化；类、方法和字段名称没有改变。 2.如何迁移这里推荐借助 Android Studio 3.2 及更高版本，您可以通过从菜单栏中依次选择Refactor > Migrate to AndroidX，快速迁移现有项目以使用 ...

参与评论您还未登录，请先登录后发表或查看评论

android studio java.exe finished with non-zero exit value 2 解决思路与方法

zrbcsdn的专栏

12-18

1346

android studio上编译运行项目会遇到很多奇葩的错误，不得不说，这是一种折磨。虽然android studio上添加第三方灰常方便，只需要一行代码，但是各种冲突的情况也增加了。貌似都是gradle配置的问题。好了，废话不多说，看问题吧：经典问题，也是常出问题：android studio java.exe finished with non-zero exit value 2。出

Process ‘command ‘C:\Program Files\Java\jdk1.8.0_51\bin\java.exe‘‘ finished with non-zero exit 报错解决

HubertToLee的博客

12-09

9633

> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.8.0_51\bin\java.exe'' finished with non-zero exit value 2 这错我是在graddle项目中遇到了，初始的时候百度查了下，全是一堆废话，他们的解决方式千篇一律是在build

finished with non-zero exit value 1

liugec的博客

05-07

9662

Android studio 编译问题：finished with non-zero exit value 1（由于导入的依赖出现重复造成的）

java.exe finished with non-zero exit value 1 问题引申

spring123tt的专栏

12-12

7742

今天导入layoutlib.jar，在eclipse上没有啥问题，但是在android studio 上就是如下的问题： Error:Execution failed for task ':dexAppDebug'.> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecE

Android Studio编译大工程报错：java.exe'' finished with non-zero exit value 1

热门推荐

serapme的专栏

06-29

5万+

困扰了三天的Android Studio编译报错终于解决了！三天尝试了各种不同的方案针对各个不同的方方面面，然而真相只有一个！原问题情景：由于项目工程特别大，在编译一段后就会报下面这个错误：Error:Execution failed for task ':dexAppDebug'. > com.android.ide.common.process.ProcessException: org

React Native ------遇坑记

silently_frog的博客

10-25

1018

版本： react-native 0.61.0 react-native-cli:2.0.1 ; node:v12.13.0 问题一：(不一样的错误，服务闪退) unable to load script from assets "index.android.bundle" 网上解决办法有两种： 1. Js serve...

centos7安装配置mysql的正确姿势

wenbingping的专栏

01-22

2052

centos 安装mysql其实是很基础的事情，但是花了大半天时间，用网上很多教程都没有安装成功，这里却安装成功了，因此进行记录。

Android连接器(三)-Android 程序加载运行-链接器实现

woai110120130的专栏

05-04

1231

/* * This is the entry point for the linker, called from begin.S. This * method is responsible for fixing the linker's own relocations, and * then calling __linker_init_post_relocation(). * * Because this method is called before the linker has fixed i

android studio finished with non-zero exit value 1， value 2解决办法

12-12

解决androidstudio中出现finished with non-zero exit value 1，或者finished with non-zero exit value 2的问题

Process 'command 'C:\Program Files\Java\jdk1.8.0_51\bin\java.exe'' finished with non-zero exit value

魏小埋的博客

02-12

6467

"com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.8.0_60\bin\java.exe'' finished with non-zero exit value 2"

安卓编译出错： Process 'command 'C:\Java\jdk1.8.0_51\bin\java.exe'' finished with non-zero exit value 1 解决！...

weixin_30236595的博客

11-08

2980

安卓编译出错： Process 'command 'C:\Java\jdk1.8.0_51\bin\java.exe'' finished with non-zero exit value 1 解决！刚从eclipse转到Android studio，安装完成之后搭建了系统默认的hello world代码工程，却出现了以下错误： Process 'command 'C:\...

解决C:\Program Files\Java\jdk1.7.0_71\bin\java.exe'' finished with non-zero exit value 2

aengui的博客

11-24

1万+

使用android studio 导入了一个别人的module， gradle的时候就报了个错，完整错误信息为 Error:Execution failed for task ':app:transformClassesWithDexForDebug'. > com.android.build.api.transform.TransformException: com.android.

Android Studio运行工程报错：java.exe'' finished with non-zero exit value 1

wyyl1的专栏

11-07

1738

转自：http://blog.csdn.net/serapme/article/details/46685557 报错信息例如： java.exe'' finished with non-zero exit value 1 java.exe'' finished with non-zero exit value 2 java.exe'' finished with non-ze

Process 'command 'E:\androidStudioSpec\jre\bin\java.exe'' finished with non-zero exit value 1

MarkRZJ的博客

04-01

626

一个非常离奇的 bug , Google 许久无果，看到 stackoverflow 有个回答是设置 dex 分包的配置，猜想可能是和 dex 分包有问题，果断删除以下的 dex 分包配置，果然运行成功。 dexOptions { javaMaxHeapSize "4g" preDexLibraries = false additionalParameters += ...

Android错误知识汇总

俊光的专栏

02-20

845

1.Android Studio com.android.dex.DexException: Multiple dex files define(重复引用包) 解决方法：在gradle文件中改，只需要将重复的引用中的compile改成provided就行。 2.AS中运行项目时出现Error： Execution failed for task ‘：app：transformClas

kafka Process ‘command ‘/jdk1.8.0_77/jre/bin/java.exe finished with non-zero exit value 1

qq_31686241的博客

06-03

1203

kafka 源码 Execution failed for task ':core:Kafka.main()'. > Process 'command 'C:/Program Files/Java/jdk1.8.0_77/jre/bin/java.exe'' finished with non-zero exit value 1

Process ‘command ‘C:/Program Files/Java/jdk1.8.0_192/bin/java.exe‘‘ finished with non-zero exit valu

LuoBeicheng的博客

02-14

6024

Process ‘command ‘C:/Program Files/Java/jdk1.8.0_192/bin/java.exe’’ finished with non-zero exit value 1 解决

returned non-zero exit status 1

03-31

This error message indicates that a command or program that was run in a terminal or script did not complete successfully. The "non-zero exit status" refers to the error code returned by the command, which is a number that indicates the specific type of error that occurred. In this case, the error code was 1, which is a common code used to indicate a generic error or failure. To troubleshoot this issue, you will need to investigate the specific command or program that returned the error and determine what went wrong. This may involve reviewing any error messages or logs generated by the command, checking the input parameters or configuration settings, and verifying that any required dependencies or resources are available. Depending on the nature of the error, you may need to modify the command or script to fix the issue, or seek assistance from a more experienced user or support resource.