Unable to import libraries to my maven project with IntelliJ 2019.2.1

Answered

Exact same maven project is successfully imported with Community 2018.2.3.

However, when trying to import it with 2019.2.1, getting all reds.

When I go to project structure, to the libraries tab, I see that there are no libraries.

As opposed to my 2018 community version where I can see all the libraries imported.

Needless to say that I am successfully compiling and building it outside of intelliJ.

This log keeps on appearing in the idea.log file:

 

2019-09-04 08:08:29,206 [43849879] INFO - #org.jetbrains.idea.maven - org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/eclipse/aether/RepositorySystemSession;
java.lang.NoSuchMethodError: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/eclipse/aether/RepositorySystemSession;
at org.jetbrains.idea.maven.server.Maven3ServerEmbedder.createMavenSession(Maven3ServerEmbedder.java:367)
at org.jetbrains.idea.maven.server.Maven3ServerEmbedder.executeWithMavenSessionLegacy(Maven3ServerEmbedder.java:351)
at org.jetbrains.idea.maven.server.Maven30ServerEmbedderImpl.executeWithMavenSession(Maven30ServerEmbedderImpl.java:601)
at org.jetbrains.idea.maven.server.Maven30ServerEmbedderImpl.doResolveProject(Maven30ServerEmbedderImpl.java:616)
at org.jetbrains.idea.maven.server.Maven30ServerEmbedderImpl.resolveProject(Maven30ServerEmbedderImpl.java:573)
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)

 

Appreciate any help.

Thank you.

 

2
9 comments

Which version of Maven are you using? Try using the latest.

1

Using 3.0.4.

Using newer version does solve this!

However, since this is a corporate custom version, I can't seem to build the project (inside intelliJ) with this newer version.

I did reinstate the older maven version and now everything seems to work.

Thanks for the help.

 

1

It was strange, but it looks like in my case switching to installed maven instead of bundled didn't help. But switch to it, and then back to bundled, and the problem disappeared.

So I had the problem, when using bundled maven, and now I'm again using bundled maven, and problem is gone.

1

I am having the same issue and the same logs when using maven-3.0.5. Everything was working last week, but I think the recent update broke it somehow. What is the solution?

IntelliJ IDEA 2019.2.1 (Ultimate Edition)
Build #IU-192.6262.58, built on August 20, 2019

0

Use bundled maven, and problem will dissapear.

0

Hi I need help seriously, having same problem on both 2018.2 ( so I decided to update ) and also 2019.3

  • IntelliJ IDEA 2019.3 Build #IU-193.5233.102
    2019-12-16 18:10:55,010 [ 253708] ERROR - #org.jetbrains.idea.maven - JDK: 11.0.4; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o
    2019-12-16 18:10:55,010 [ 253708] ERROR - #org.jetbrains.idea.maven - OS: Mac OS X
  • see my /etc/hosts
    # Host Database
    #
    # localhost is used to configure the loopback interface
    # when the system is booting. Do not change this entry.
    ##
    127.0.0.1 localhost
    255.255.255.255 broadcasthost
    ::1 localhost

    192.168.30.68 test-beheertool.hdn.local

    # ADFS - needed while running home over VPN
    192.168.100.20 ad-sharedlab.dvsktest.local

    # ****cloud-dev LDAP
    172.30.*.* ldap-dev-a.dev-net.****cloud.nl

    127.0.0.1 ads.viber.com
    ::1 ads.viber.com

  • mvn 3.6.3 - fresh, pure
  • ~/.m2/settings.xml - absolutely without any problems last 6 years
  • java version "1.8.0_231"
    Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
    Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)
  • echo $JAVA_HOME
    /Library/Java/JavaVirtualMachines/jdk1.8.0_231.jdk/Contents/Home
  • but Idea still Unable to import Maven project
  • switching my or bundled vn does not help
  • I read almost all history of this problem foundable on web, nothing helped me


2019-12-16 18:10:54,653 [ 253351] WARN - ution.rmi.RemoteProcessSupport - java.rmi.NotBoundException: _DEAD_HAND_
2019-12-16 18:10:54,654 [ 253352] WARN - ution.rmi.RemoteProcessSupport - at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:227)
2019-12-16 18:10:54,654 [ 253352] WARN - ution.rmi.RemoteProcessSupport - at com.intellij.execution.rmi.RemoteServer.start(RemoteServer.java:93)
2019-12-16 18:10:54,654 [ 253352] WARN - ution.rmi.RemoteProcessSupport - at org.jetbrains.idea.maven.server.RemoteMavenServer36.main(RemoteMavenServer36.java:23)
2019-12-16 18:10:55,008 [ 253706] WARN - ution.rmi.RemoteProcessSupport - The cook failed to start due to java.io.EOFException
2019-12-16 18:10:55,009 [ 253707] ERROR - #org.jetbrains.idea.maven - Cannot reconnect.
java.lang.RuntimeException: Cannot reconnect.
at org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:82)
at org.jetbrains.idea.maven.server.MavenServerManager.applyProfiles(MavenServerManager.java:485)
at org.jetbrains.idea.maven.project.MavenProjectReader.applyProfiles(MavenProjectReader.java:385)
at org.jetbrains.idea.maven.project.MavenProjectReader.doReadProjectModel(MavenProjectReader.java:94)
at org.jetbrains.idea.maven.project.MavenProjectReader.access$300(MavenProjectReader.java:37)
at org.jetbrains.idea.maven.project.MavenProjectReader$1.doProcessParent(MavenProjectReader.java:439)
at org.jetbrains.idea.maven.project.MavenProjectReader$1.doProcessParent(MavenProjectReader.java:415)
at org.jetbrains.idea.maven.project.MavenParentProjectFileProcessor.processRepositoryParent(MavenParentProjectFileProcessor.java:84)
at org.jetbrains.idea.maven.project.MavenParentProjectFileProcessor.process(MavenParentProjectFileProcessor.java:62)
at org.jetbrains.idea.maven.project.MavenProjectReader.resolveInheritance(MavenProjectReader.java:442)
at org.jetbrains.idea.maven.project.MavenProjectReader.doReadProjectModel(MavenProjectReader.java:91)
at org.jetbrains.idea.maven.project.MavenProjectReader.readProject(MavenProjectReader.java:53)
at org.jetbrains.idea.maven.project.MavenProject.read(MavenProject.java:682)
at org.jetbrains.idea.maven.project.MavenProjectsTree.doUpdate(MavenProjectsTree.java:551)
at org.jetbrains.idea.maven.project.MavenProjectsTree.doAdd(MavenProjectsTree.java:497)
at org.jetbrains.idea.maven.project.MavenProjectsTree.update(MavenProjectsTree.java:458)
at org.jetbrains.idea.maven.project.MavenProjectsTree.updateAll(MavenProjectsTree.java:429)
at org.jetbrains.idea.maven.project.MavenProjectsProcessorReadingTask.perform(MavenProjectsProcessorReadingTask.java:61)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor.doProcessPendingTasks(MavenProjectsProcessor.java:141)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor.access$000(MavenProjectsProcessor.java:35)
at org.jetbrains.idea.maven.project.MavenProjectsProcessor$1.run(MavenProjectsProcessor.java:110)
at org.jetbrains.idea.maven.utils.MavenUtil.lambda$runInBackground$5(MavenUtil.java:482)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:238)
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)
Caused by: java.rmi.RemoteException: Cannot start maven service; nested exception is:
java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)
at org.jetbrains.idea.maven.server.MavenServerManager.create(MavenServerManager.java:259)
at org.jetbrains.idea.maven.server.MavenServerManager.create(MavenServerManager.java:77)
at org.jetbrains.idea.maven.server.RemoteObjectWrapper.getOrCreateWrappee(RemoteObjectWrapper.java:41)
at org.jetbrains.idea.maven.server.MavenServerManager.lambda$applyProfiles$8(MavenServerManager.java:485)
at org.jetbrains.idea.maven.server.RemoteObjectWrapper.perform(RemoteObjectWrapper.java:76)
... 27 more
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)
at java.rmi/sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at java.rmi/sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:209)
at java.rmi/sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:196)
at java.rmi/sun.rmi.server.UnicastRef.newCall(UnicastRef.java:338)
at java.rmi/sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java:112)
at com.intellij.execution.rmi.RemoteProcessSupport.lambda$acquire$2(RemoteProcessSupport.java:243)
at com.intellij.openapi.util.ClassLoaderUtil.computeWithClassLoader(ClassLoaderUtil.java:45)
at com.intellij.execution.rmi.RemoteUtil.executeWithClassLoader(RemoteUtil.java:219)
at com.intellij.execution.rmi.RemoteProcessSupport.acquire(RemoteProcessSupport.java:241)
at com.intellij.execution.rmi.RemoteProcessSupport.acquire(RemoteProcessSupport.java:148)
at org.jetbrains.idea.maven.server.MavenServerManager.create(MavenServerManager.java:247)
... 31 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
at java.base/java.net.Socket.connect(Socket.java:591)
at java.base/java.net.Socket.connect(Socket.java:540)
at java.base/java.net.Socket.<init>(Socket.java:436)
at java.base/java.net.Socket.<init>(Socket.java:213)
at com.intellij.execution.rmi.RemoteServer$1.createSocket(RemoteServer.java:120)
at java.rmi/sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
... 41 more
2019-12-16 18:10:55,010 [ 253708] ERROR - #org.jetbrains.idea.maven - IntelliJ IDEA 2019.3 Build #IU-193.5233.102
2019-12-16 18:10:55,010 [ 253708] ERROR - #org.jetbrains.idea.maven - JDK: 11.0.4; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o
2019-12-16 18:10:55,010 [ 253708] ERROR - #org.jetbrains.idea.maven - OS: Mac OS X

0

@Mkubincanek You may have ESET Endpoint Security or similar tool installed which blocks all the connections on localhost. Please disable the antivirus/firewall and see if it helps.

0

Thanks for response, I made complete hard-reboot of OS X ( Mojave to Catalina with complete HD erase and backup before it ) before I read your response. On fresh/clean OS I encountered same problem after I installed ESET - delegated it on OPS department, after investigation found Idea java-processes which are making some IPv4/v6 requests which were not aligned with policy defined in ESET. So ESET was problem - you were right.

0

Please sign in to leave a comment.