Maven IntelliJ错误:无法导入Maven项目。查看日志以获取详细信息

时间:2018-11-15 14:09:51

标签: java maven intellij-idea

我正在基于IntelliJ idea 2016.3.4的基于Maven的项目上工作,并在添加依赖项时收到以下错误。

Unable to import maven project: See logs for details.

idea.log文件重复包含以下日志:

role: org.apache.maven.artifact.resolver.ArtifactResolver
roleHint: ide 
java.lang.RuntimeException: java.lang.RuntimeException: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
java.util.NoSuchElementException
  role: org.apache.maven.artifact.resolver.ArtifactResolver
roleHint: ide
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.getComponent(Maven3ServerEmbedderImpl.java:475)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customizeComponents(Maven3ServerEmbedderImpl.java:552)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customize(Maven3ServerEmbedderImpl.java:529)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:162)
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
at com.sun.proxy.$Proxy125.customize(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.execution.rmi.RemoteUtil.invokeRemote(RemoteUtil.java:169)
at com.intellij.execution.rmi.RemoteUtil.access$300(RemoteUtil.java:36)
at com.intellij.execution.rmi.RemoteUtil$2$1$1.compute(RemoteUtil.java:150)
at com.intellij.execution.rmi.RemoteUtil.executeWithClassLoader(RemoteUtil.java:226)
at com.intellij.execution.rmi.RemoteUtil$2$1.invoke(RemoteUtil.java:147)
at com.sun.proxy.$Proxy125.customize(Unknown Source)
at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.doCustomize(MavenEmbedderWrapper.java:103)
at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.access$000(MavenEmbedderWrapper.java:38)
at org.jetbrains.idea.maven.server.MavenEmbedderWrapper$2.execute(MavenEmbedderWrapper.java:69)
at org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:76)
at org.jetbrains.idea.maven.server.MavenEmbedderWrapper.customizeForResolve(MavenEmbedderWrapper.java:66)
at org.jetbrains.idea.maven.project.MavenProjectsTree.resolve(MavenProjectsTree.java:1253)
at org.jetbrains.idea.maven.project.MavenProjectsProcessorResolvingTask.perform(MavenProjectsProcessorResolvingTask.java:44)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor.doProcessPendingTasks(MavenProjectsProcessor.java:130)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor.access$000(MavenProjectsProcessor.java:30)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor$2.run(MavenProjectsProcessor.java:105)
at org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:458)
at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:309)
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)
Caused by: java.lang.RuntimeException: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
java.util.NoSuchElementException
  role: org.apache.maven.artifact.resolver.ArtifactResolver
roleHint: ide
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.getComponent(Maven3ServerEmbedderImpl.java:472)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customizeComponents(Maven3ServerEmbedderImpl.java:552)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedderImpl.customize(Maven3ServerEmbedderImpl.java:529)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.NoSuchElementException
at java.util.Collections$EmptyIterator.next(Collections.java:4189)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263)
... 21 more
2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - 
 IntelliJ IDEA 2016.3.4  Build #IU-163.12024.16 
2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - JDK: 1.8.0_112-release 
 2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - VM: OpenJDK Server VM 
 2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - Vendor: JetBrains s.r.o 
2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - OS: Windows 10 
2018-11-15 18:32:37,925 [ 379691]  ERROR -      #org.jetbrains.idea.maven - Last 
Action: EditorPaste  

我尝试创建新的项目,并提到了here的解决方案。

但是我仍然遇到相同的错误。

有什么办法解决这个问题?

4 个答案:

答案 0 :(得分:0)

您可以将您编写的依赖代码放在这里吗? 您的pom可能格式不正确 顺便说一句,您的pom中应该有类似的内容:

 <dependencyManagement>
    <dependencies>
        <dependency>
            <!--<your dependecy>-->
            <groupId></groupId>
            <artifactId></artifactId>
            <version></version>
            <!--<your dependecy>-->
        </dependency>
        ...other dependencies....
    </dependencies>
</dependencyManagement>

我还看到了一些可以通过maven-compat插件解决的查找错误:

<dependency>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven-compat</artifactId>
    <version>3.0.5</version>
    <scope>test</scope>
</dependency>

您的问题也可能是由您的代码生成的,当您尝试执行NoSuchElementException或元素的下一个而没有执行时,Object就会发生 检查您的周期。 我说不出更多的信息,很高兴看到代码和pom。

答案 1 :(得分:0)

我仍然不知道问题出在哪里,但是重新启动PC后问题已经解决。 Intellij工作正常,Maven现在正在导入。

答案 2 :(得分:0)

也许您可以尝试更新您的想法

当我将2019.2.1更新为2019.2.4并自行解决问题时

答案 3 :(得分:0)

我从项目目录中删除了 .idea 文件夹并重新导入了项目。问题消失了。