[坑] IDEA Unable to import maven project 解决办法
缘起
今天给一台电脑新安装了idea顺便进行了简单的Maven配置,我是用的是idea2017版本以及maven3.6.2的版本,习惯性的安装软件都食用最新版本。
安装完在cmd里面输入命令mvn -v是没有任何问题,简简单单那接下来就是配置到IDEA然后跑一个项目测试下 ヾ(≧▽≦*)o
然后就出现了这个......
解决
我可以确定一定以及肯定是,我的maven的本地仓库配置以及idea里面maven版本的地址没有一点的问题。但是一创建maven项目以后就报这个错误;
遂求助万能的度娘,刚开始是直接搜的IDEA Unable to import maven project 解决办法,但是他们分析下来的原因都是五花八门的一一对应和我的都不一样,但是有一个相同的一点是他们都是分析了log错误文件分析出了原因
;
开始埋头查看日志文件......
1) No implementation for org.apache.maven.model.path.PathTranslator was bound. while locating org.apache.maven.model.path.PathTranslator for field at org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown Source) at org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350) 2) No implementation for org.apache.maven.model.path.UrlNormalizer was bound. while locating org.apache.maven.model.path.UrlNormalizer for field at org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown Source) at org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350) 2 errors java.lang.RuntimeException: com.google.inject.CreationException: Unable to create injector, see the following errors: 1) No implementation for org.apache.maven.model.path.PathTranslator was bound. while locating org.apache.maven.model.path.PathTranslator for field at org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown Source) at org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350) 2) No implementation for org.apache.maven.model.path.UrlNormalizer was bound. while locating org.apache.maven.model.path.UrlNormalizer for field at org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown Source) at org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350) 2 errors at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:159) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106) at com.google.inject.Guice.createInjector(Guice.java:87) at com.google.inject.Guice.createInjector(Guice.java:69) at com.google.inject.Guice.createInjector(Guice.java:59) at org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344) at org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:332) at org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customizeComponents(Maven3XServerEmbedder.java:573) at org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customize(Maven3XServerEmbedder.java:542) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) at java.rmi/sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283) at java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260) at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209) at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161) at com.sun.proxy.$Proxy149.customize(Unknown Source) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.intellij.execution.rmi.RemoteUtil.invokeRemote(RemoteUtil.java:175) at com.intellij.execution.rmi.RemoteUtil.access$200(RemoteUtil.java:38) at com.intellij.execution.rmi.RemoteUtil$1$1$1.compute(RemoteUtil.java:156) at com.intellij.openapi.util.ClassLoaderUtil.computeWithClassLoader(ClassLoaderUtil.java:45) at com.intellij.execution.rmi.RemoteUtil.executeWithClassLoader(RemoteUtil.java:227) at com.intellij.execution.rmi.RemoteUtil$1$1.invoke(RemoteUtil.java:153) at com.sun.proxy.$Proxy149.customize(Unknown Source) at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:92) at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.onWrappeeCreated(MavenEmbedderWrapper.java:45) at org.jetbrains.idea.maven.server.RemoteObjectWrapper.getOrCreateWrappee(RemoteObjectWrapper.java:42) at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:92) at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.lambda$customizeForResolve$1(MavenEmbedderWrapper.java:65) at org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:76) at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.customizeForResolve(MavenEmbedderWrapper.java:64) at org.jetbrains.idea.maven.project.MavenProjectsTree.resolve(MavenProjectsTree.java:1261) at org.jetbrains.idea.maven.project.MavenProjectsProcessorResolvingTask.perform(MavenProjectsProcessorResolvingTask.java:45) at org.jetbrains.idea.maven.project.MavenProjectsProcessor.doProcessPendingTasks(MavenProjectsProcessor.java:140) at org.jetbrains.idea.maven.project.MavenProjectsProcessor.access$000(MavenProjectsProcessor.java:33) at org.jetbrains.idea.maven.project.MavenProjectsProcessor$2.run(MavenProjectsProcessor.java:114) at org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:468) at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:294) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
最终
看不太懂,什么无法创建注射器...什么未知源......一头雾水
带着log去问度娘,查到最新的3.6.2的model builder 使用了JSR 330进行依赖注入,不再使用plexus
Maven 3.6.2 发行说明
问题就是因为这个新技术出现了兼容性的问题,尝试回退到3.5.2重新安装配置问题解决!
虽然还是不懂是为什么,什么是JSR 330依赖注入但总算是不报错了,散了散了~
要学会多看日志文件呀 英语太重要了不能落下呀
[坑] IDEA Unable to import maven project 解决办法相关推荐
- Unable to import maven project: See logs for details错误解决方法
Unable to import maven project: See logs for details错误解决方法 Unable to import maven project: See logs ...
- idea Maven报Unable to import maven project: See logs for details解决方法
问题描述: 从github/svn/git上下拉下来的项目,在maven更新中,idea会抛出Unable to import maven project: See logs for details错 ...
- IDEA创建springboot项目:Unable to import maven project: See logs for details
Bug介绍: 之前用的IDEA2020,然后使用的maven3.6.3,后来IDEA换为了2017.3.6,今天创建项目时居然一直报错Unable to import maven project: S ...
- idea会抛出Unable to import maven project: See logs for details错误
问题描述: 从github/svn/git上下拉下来的项目,在maven更新中,idea会抛出Unable to import maven project: See logs for details错 ...
- 控制台:Unable to import maven project: See logs for details日志:Unable to create injector, see the follow
问题描述: 当我在使用IDEA 完成一个Maven项目的时候,在第一步的pom.xml文件导入依赖时就发生了这个问题,弹窗弹出Uable to import maven project 控制台报 Un ...
- IDEA Maven 报 Unable to import maven project解决方案
IDEA Maven 报 Unable to import maven project解决方案 问题: 解决: 问题: 将同事给的项目放在自己电脑IDEA里,加载时一直报Unable to impor ...
- IDEA中新导入的项目找不到maven project解决办法
刚导入的项目,导入进来之后,找不到maven project,idea打开view ->tool windows下也没有maven模块.查看了setting下plugins中maven插件也在. ...
- 第一次创建maven项目时报错:Unable to import Maven project See logs for details
在网上看了很多版本,有说Maven版本和idae版本不匹配的,也有说重启一下项目的.但是这些都没有解决我的问题:最后我是这样解决的: 把画红线的地方改成自己的jdk即可.
- 刷新maven project报错: unable to import maven project ,see logs fot details
本地报错 是因为 idea2018与 tomcat3.6.3版本不兼容的问题. 重新下载一个tomcat3.5.2版本,问题解决. 附上tomcat3.5.2版本下载地址: https://archi ...
最新文章
- python的print换行
- IT-标准化-系列-0.课程-V1.0
- WCF传送大数据时的错误“ 超出最大字符串内容长度配额”
- A. Many Equal Substrings(自己很水)
- CMS:文章管理之视图(2)
- Mysql InnoDB 数据更新/删除导致锁表
- for range 经典问题
- php读取mp3信息,PHP获取MP3的媒体标签信息
- ASP.NET Core 源码学习之 Logging[3]:Logger
- 组策略对应于注册表位置汇总
- 阿里云cloudmonitor服务导致CPU暴增的异常
- Spring系列(三) Bean装配的高级技术
- opengl (1) 基本API的熟悉
- PHP面向对象之方法重写
- 【WPF扁平化界面设计】
- 深度| 百度副总裁王海峰:百度在NLP领域都做了什么?
- Worthington核糖核酸酶B历史和化学性质说明
- Redis源码分析之双索引机制
- 【天下有春】剑气纵横三万里,一剑光寒十九洲
- 容联云通讯php短信接口,开发中使用 【容联 云通信】获取短信验证码的 Javascript 接口...