IntelliJ 14 maven compilation issues

Question

I have updated to IntelliJ 14.0.1 today. I imported the Maven project I was working on IntelliJ 13.1 and although the project is imported successfully the dependencies cannot be found when I try to Make or Compile the project from IntelliJ.

I need to say that when I do a Maven install, even from inside IntelliJ, that is successful. But when I Make the project errors occur indicating that libraries (dependencies) are missing.

It seems to me that somehow the compilation step from IntelliJ does not pick up the Maven dependencies or is not taking the pom.xml into consideration.

Has anyone faced something similar? Any ideas on how to fix that? I have already tried re importing the project but didn't help. Additionally I have created a dummy project with only JUnit as a dependency but even then IntelliJ is complaining that it cannot find org.junit.Test when I try to run my tests.

UPDATE:

I see the following in the IntelliJ logs, which might be related. Seems like the compilation is aborted.

2014-11-14 17:17:11,460 [ 247914] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: 17:17:11,445 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.groovy] at [jar:file:/C:/Program%20Files%20(x86)/JetBrains/IntelliJ%20IDEA%20Community%20Edition%2014.0.1/plugins/gradle/lib/gradle.jar!/logback.groovy]

2014-11-14 17:17:11,460 [ 247914]   INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: 17:17:11,446 |-ERROR in ch.qos.logback.classic.LoggerContext[default] - Groovy classes are not available on the class path. ABORTING INITIALIZATION.

2014-11-14 17:17:13,459 [ 249913]   INFO - lij.compiler.impl.CompilerUtil -              COMPILATION FINISHED (BUILD PROCESS); Errors: 5; warnings: 0 took 2652 ms: 0 min 2sec

Answer 1

For the sake of others, my problem had to do with the location of the Maven repository. My Maven repository was in a network drive and apparently IntelliJ cannot read from UNC paths.

The fact that it cannot read from the UNC path is not really obvious and requires careful examination of the IntelliJ logs.

The obvious solution was to move the Maven Repo to the C:\drive.

Answer 2

Disable the Maven 3 checkbox in "Settings | Maven | Importing". You may then need to change the POM by adding a blank line and reimport.

This advice was taken from a previous problems reported when upgrading from ver 12 to 13. Thanks to user SchraderMJ11

Answer 3

I've had the same issue.

I've done "Reimport all Maven Projects" from Maven project window. That resolved the issue.

When ever you do a new pull or changes in to the project, you need to reimport from the Maven Prjoct window. It helps IntelliJ to get all the dependencies properly in place for building the project.

Hope this helps.