maven安装出现错误:ERROR: JAVA_HOME is set to an invalid directory.

最新推荐文章于 2025-01-08 15:51:07 发布
转载 最新推荐文章于 2025-01-08 15:51:07 发布 · 139 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/IntelligentBrain/p/5111340.html
文章标签：

#java

本文介绍在Maven安装过程中遇到的JAVA_HOME环境变量配置问题及解决方案。通过将文件夹名称从jdk1.6.0_06修改为jdk并重新配置环境变量解决了maven识别问题。

maven安装过程中常常出现java环境变量配置出错的问题,(出现这个问题的可能性很多,下面是我遇到的问题)
ERROR: JAVA_HOME is set to an invalid directory.
JAVA_HOME = "D:\Program Files\Java\jdk1.6.0_06"
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation

截图如下:

我的错误比较特殊:把文件夹:jdk1.6.0_06文件夹改为jdk,再重新配置环境变量就可以搞定了,问题解决,可能是maven识别较弱的问题吧

转载于:https://www.cnblogs.com/IntelligentBrain/p/5111340.html

Error: JAVA_HOME is set to an invalid directory.
天马3798
03-13 4553
一、问题：新版本Cordova 命令启动android应用报错 当前Cordova V11.0 Error: JAVA_HOME is set to an invalid directory. 此问题原因是Java_Home 环境变量配置有问题，配置目录中不能有bin文件夹。 二、解决方案： 正确的配置方式：Java_Home C:\Program Files\Android\jdk\jdk-8.0.302.8-hotspot\jdk8u302-b08\ 更多： VS Co.
出现Maven home directory is invalid 或者No valid Maven installation found. Either set the home等的解决方法（万能）
码农研究僧的博客
11-30 5856
Error running ‘012-springboot-mybatis [org.mybatis.generator:mybatis-generator-maven-plugin:1.3.6:generate]’: Maven home directory is invalid: B:\java配置文件\apache-maven-3.8.1
gradle -version ERROR:JAVA_HOME is set to an invalid directory
android_panda的时间
03-17 1万+
gradle -version 出错的JAVA_HOME设置为：  D:\program files\Java\jdk1.7.0_21;   出错如下图： 修改JAVA_HOME设置为：D:\program files\Java\jdk1.7.0_21（去掉了后面的分号），错误解决。 具体原因：不清楚。两个字坑爹。
配置maven出现JAVA_HOME is set to an invalid directory.
tvvbbb的专栏
12-10 3916
网上说的什么没有分号那些，抄来抄去的我就不说了，这些我都没有问题，最后发现在java_home里面要加入jre在后面，在我的机器就是D:/software/JDK/jre，这样就好了，要注意不要加入分号（；）不然就不行了
Error: JAVA_HOME is set to an invalid directory.-解决办法
热门推荐
qq_31285709的博客
09-04 2万+
安装好Maven运行mvn -v之后出现错误： Error: JAVA_HOME is set to an invalid directory. JAVA_HOME = “D:\Others\java\jdk1.8.0_181\bin” Please set the JAVA_HOME variable in your environment to match the location of y...
FO: Starting Servlet Engine: Apache Tomcat/7.0.59 Sep 03, 2025 1:28:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs Sep 03, 2025 1:28:09 PM org.apache.catalina.startup.ContextConfig processAnnotationsJar SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] from Jar [jar:file:/data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs/WEB-INF/lib/commons-net-3.10.0.jar!/] for annotations org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19 at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97) at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:55) at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:177) at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:85) at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2089) at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1965) at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1931) at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1916) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5412) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Sep 03, 2025 1:28:10 PM org.apache.catalina.startup.TaglibUriRule body INFO: TLD skipped. URI: webwork is already defined log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/bdcs.log (No such file or directory) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:133) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:432) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460) at org.apache.log4j.LogManager.<clinit>(LogManager.java:113) at org.apache.log4j.Category.getInstance(Category.java:530) at org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:140) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:257) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390) at com.opensymphony.clickstream.ClickstreamListener.<clinit>(ClickstreamListener.java:24) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:116) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4932) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) log4j:ERROR Either File or DatePattern options are not set for appender [bdcs]. 09-03 13:28:11.438 INFO [ContextLoader.java:142] Root WebApplicationContext: initialization started 09-03 13:28:11.457 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/sso/test_sso_context.xml] 09-03 13:28:11.479 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/exporthr/test_exporthr_context.xml] 09-03 13:28:11.486 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/prodtech/prod_prodtech_context.xml] 09-03 13:28:11.500 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/bdcs/mail_content.xml] 09-03 13:28:11.501 ERROR [ContextLoader.java:172] Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [com/smics/apps/bdcs/mail_content.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/smics/apps/bdcs/mail_content.xml] cannot be opened because it does not exist java.io.FileNotFoundException: class path resource [com/smics/apps/bdcs/mail_content.xml] cannot be opened because it does not exist at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:127) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:99) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:114) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:82) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:87) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:262) at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:131) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:224) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:150) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:48) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5016) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)什么原因
最新发布
09-04
我们面对的是一个Tomcat启动时的错误日志，主要包含两类错误： 1. SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] ... Invalid byte tag in constant pool: 19 2. 后续的log4j错误...
Error: Unable to determine the current character, it is not a string, number, array, or object in...
suiusoar
01-08 910
错误：无法确定当前字符，它不是字符串、数字、数组或对象，在 React Native for Android 中。
idea中Exception in thread “main“ java.lang.UnsatisfiedLinkError: org.apache.hadoop.io.nativeio.Native
qq_56572867的博客
04-02 944
这个困扰了我三天的问题，之前已经不想解决了，直到再一次遇到，决定彻底干它，之前也在网上搜了一些解决它的办法，什么改变环境还有加入NativeIO，都没有用，不过最后还是使用了NativeIO的方法解决了，之前一直没有用的原因是，没有把文件放对位置 正确的位置应该是放在java包下，和项目包并行，而且必须是这个包名org.apache.hadoop.io.nativeio和NativeIO这个类名，不然不能覆盖原来的这个类 下面附上NativeIO的源码，有的包可能要自己引一下，细节上应该不用说了
Error opening data file /tessdata/eng.traineddata Please make sure the TESSDATA_PREFIX environment variable is set to the parent directory of your "tessdata" directory. Failed loading language 'eng' Error opening data file /tessdata/chi_sim.traineddata Please make sure the TESSDATA_PREFIX environment variable is set to the parent directory of your "tessdata" directory. Failed loading language 'chi_sim' Tesseract couldn't load any languages! Exception in thread "main" java.lang.Error: Invalid memory access at com.sun.jna.Native.invokePointer(Native Method) at com.sun.jna.Function.invokePointer(Function.java:470) at com.sun.jna.Function.invoke(Function.java:404) at com.sun.jna.Function.invoke(Function.java:315) at com.sun.jna.Library$Handler.invoke(Library.java:212) at jdk.proxy1/jdk.proxy1.$Proxy0.TessBaseAPIGetUTF8Text(Unknown Source) at net.sourceforge.tess4j.Tesseract.getOCRText(Unknown Source) at net.sourceforge.tess4j.Tesseract.doOCR(Unknown Source) at net.sourceforge.tess4j.Tesseract.doOCR(Unknown Source) at net.sourceforge.tess4j.Tesseract.doOCR(Unknown Source) at OCRDemo.main(OCRDemo.java:17) 进程已结束，退出代码为 1
08-06
首先，用户的问题是关于Tesseract OCR的错误：加载语言文件失败，出现"Error opening data file"、"Failed loading language 'eng' and 'chi_sim'"，以及"Invalid memory access"错误。这发生在Java环境中使用...
Error: JAVA_HOME is set to an invalid directory.解决方法
qq_43786558的博客
03-23 6543
Error: JAVA_HOME is set to an invalid directory.解决方法
ERROR: JAVA_HOME is set to an invalid directory 以及‘javac‘ 不是内部或外部命令，也不是可运行的程序解决
weixin_44976890的博客
07-30 1万+
ERROR: JAVA_HOME is set to an invalid directory 以及’javac’ 不是内部或外部命令，也不是可运行的程序解决 结论在这里插入代码片：这两个问题都是jdk环境变量配置的有问题。 解决方法：需要修改java_home和path的配置。 报错： 这里为了模拟错误，我改了JAVA_HOME的配置，我原本报错不是路径带“；”原因【虽然也是靠修改路径解决的】，这里只是为了展示错误 进入环境变量配置 解决过程： 我的电脑右键属性，选择高级属性设置 配置JAVA_H
配置gradle时，一直报错提示：ERROR: JAVA_HOME is set to an invalid directory: D:\Java\jdk1.8.0_144;
dou_being的博客
10-13 3829
配置gradle失败，一直报错提示：ERROR: JAVA_HOME is set to an invalid directory: D:\Java\jdk1.8.0_144; 报错的原因是因为配置的JAVA_HOME后面多加了“;”。 解决方法：将JAVA_HOME后面的分号去掉，然后重新打开cmd，运行gradle -v或gradle -version， 总结：配置环境变
ERROR: JAVA_HOME is set to an invalid directory. JAVA_HOME = "D:\tools\jdk\jdk1.8.0_73" Please set t
彻底拆分，一切可控！
04-21 9451
在 mvn -v 测试自己的 maven 程序的时候，报的上面的错误，这个原因是 JAVA_HOME设置有问题。 本来经过修改 JAVA_HOME 之后 mvn -v 就成功了。 jdk 安装目录如下： 正确的 JAVA_HOME 设置如下： 因此正确的设置应该如下： JAVA_HOME ： D:\tools\Java\jdk1.8.0_73 path ： %JAV...
在命令行窗口查看Maven版本时，出现 Error: JAVA_HOME is set to an invalid directory.的解决方法...
weixin_33749131的博客
11-29 381
查看Maven版本： 结果出现： 搜索了网上的解决方法，解决了问题的方法是： 将JAVA_HOME = "D:/Java/jdk1.6.0_12/bin"修改成JAVA_HOME = "D:/Java/jdk1.6.0_12" 将path环境变量中的%JAVA_HOME%修改成%JAVA_HOME%/bin 然后重启cmd 因为Java home是在jdk1.8.0_60的...
ERROR: JAVA_HOME is set to an invalid directory
lizhong
03-20 1万+
在调试学习比较火的 热修复 BUG时，生成JAR文件报出的这个问题 刚开始的时候各种查找原因，这个问题大概意思就是没有找到这个 这里说出我的解决办法，顺便自己做个记录，就是环境变量设置问题 1、打开环境变量JAVA_HOME 这里放这个路径，我之前错误路径就是E:\AndroidHJ\Java\jdk1.8.0_201将其修改为图上路径 如果没有新建一个JAVA_HOME=C:\...
Maven错误：JAVA_HOME is set to an invalid directory.
MarryLinDa的博客
12-15 4938
mvn.cmd里的JAVA_HOME的值不是正确的java地址。
命令行执行mvn 之后提示error java_home is set to an invalid directory
qq_28854219的博客
04-09 729
问题描述： 在命令行执行mvn -v命令，提示以下错误。 Error：JAVA_HOME is set to an invalid directory. JAVA_HOME="C:\Program Files\Java\jdk1.8.0_111" Please set the JAVA_HOME variable in your environment to match the locati...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值