113
votes

I have a JDK 1.7 project with a maven dependency to a local jar in my maven repo.

I'm unable to build the project using Intellij, with the errors that a symbol cannot be found (the symbol is a class importing packages from the local jar)

But I can successfully build the project using 'mvn package'.

I've spent so much time looking for solutions, things I've already done:

  • Invalidated cache
  • 'mvn clean install' the local jar dependecy
  • Marked to 'autoload snapshots' in Intellij's maven configuration
  • Reimpoted maven in Intellij
  • Syncornized

This error happend to my couple of times before, but usually just closing the Intellij and /or doing the 'mvn clean install' did the trick.

Please help.

28
Is your maven repository correctly configure with IntelliJ ?Ruchira Gayan Ranaweera
yes it is, the path for the repository is the one that is updated when I use 'mvn install'Yarin Miran
The local jar is a snapshot or a release version of jar ? If the jar is a snapshot, you must check 'Always update snapshots' into the intellij Maven settings to force the update for the ide.F. Geraerts
yes it's a snapshot, I already marked that option. But still, nothing changes :(Yarin Miran
In the Compiler part of the Settings, is the "use external build" is checked ? And in the Use external build, the "Rebuild module on dependency change" option is also checked ?F. Geraerts

28 Answers

205
votes

I know this is late but executing mvn idea:idea solves the issue.

The command re-generates the crucial IntelliJ IDEA files: ipr, iml, and iws, and thus re-align them with your pom.xml.

Documentation: https://maven.apache.org/plugins/maven-idea-plugin

The plugin is retired but still (as of 05.06.2021) works like magic :)

31
votes

Try to delete all .iml and your POM. Then copy and paste your POM again to your project and re-open and re-import it.

19
votes

Adding some more tips since this is the first thing that came up in the search when I was having similar problems (project builds in mvn, not in IntelliJ), in case it might help someone else.

When I had this it was a different fix on Windows and Mac.

On Mac, I went into ItellijIDEA / Preferences / Build, Execution, Deployment / Build Tools / Maven / Maven Home Directory and set it to use my separately installed Maven rather than the bundled Maven. All the build problems went away.

On Windows, I was seeing exceptions in the idea.log related to SSL and my project tree had only Java under the External Libraries branch. From looking at other sites it sounds like IntelliJ uses its own private JDK instead of the system one (even though in my case I already had the exact same JDK version installed). My system JDK has certs installed in the keystore for the corporate Nexus server that the IntelliJ private JDK didn't have, so exceptions were being thrown when it tried to get files from Nexus. For this the solution was to quit IntelliJ, set an environment variable called IDEA_JDK to point to the JDK I already had installed that had the proper certs and restart IntelliJ. All the build problems went away.

19
votes

Maven ReImport worked for me like below...

enter image description here

17
votes

I've found out that my .iml file and pom were conflicting and causing the issue.

10
votes

IDE uses its own bundled copy of Maven when doing builds. If maven on terminal is different from IDE, then you want them to be the same.

GOTO (On a Mac)- IntelliJ Idea -> Preferences -> Build,Execution,Deployment -> Build Tools -> Maven. Set the path for your Maven Home Directory To find the path for Maven which you use from terminal, type command mvn -version and that should print out bunch of details including the dir path. Put that in Maven Home Directory.

To be safe you can also do the same for JDK location

==== Some Other Things that can cause such issues ===

If doing mvn package or mvn clean install builds, then it has to do something with IDE caches. Among other things, this one usually helps with such errors -->

File -> Invalidate Caches

5
votes

I know I am pretty late to this conversation, but just wanted to post this in case someone else comes across this problem. Another reason why this happens is because you are not referring to the right repository. Intellij picks up the bundled version of a jar by default instead of the one from your own maven repository. Confirm that the repository connected is the right one.

3
votes

In my case my iml was not in sync, so I deleted the iml for the specific module and then under maven option select unignore project to recreate iml

3
votes

from command prompt execute the commnad : mvn idea:idea and right click on the project -> from the menu re-import the dependencies

1
votes

"symbol cannot be found" means that intellij is not able to resolve the "dependency". So, you can force "Dependency analysis" by clicking "Analyze" -> "Analyze Dependencies" then select the "Analysis Scope"

1
votes

Many valuable tips in the other answers here, just want to add the solution that worked for my problem.

We recently started using a private Maven repository and always do mvn -s settings.xml when invoking the Maven cmdline. IntelliJ does of course not know about the private repo, so it needs a little help.

Go to Settings -> Build, Execution, Deployment -> Build tools -> Maven and override the "User Settings file" option.

enter image description here

1
votes

If you are using gradle , try below command.This resolved my issue

gradle cleanIdea idea

1
votes

This simple procedure takes about 1 minute without any risc.

  • Close IntelliJ
  • Delete ONLY the IntelliJ specific files like .idea/*, *.iml, .settings, etc. Suggested was deleting the POM as well, but that is not necessary IMHO.
  • Then re-create the project in IntelliJ using: File > New > Project from existing Sources > follow the steps. Be aware NOT to import multiple profiles or (same projects).
1
votes

I had the same problem. Go to:

File -> Project Structure -> Module. Select your module and under "Dependencies" tab, make sure that all the maven dependencies are added.

To make sure you are warned about a similar issue in the idea editor: switch from "Dependencies tab" to "Sources" and add mark your src as source.

1
votes

I encountered the same problem. I can successfully run the mvn clean package command in terminal but fail to run or build from IntellJ. I did the following actions but they all failed.

  • Invalidated cache
  • run mvn clean package or mvn clean package in terminal
  • Marked to 'autoload snapshots' in Intellij's maven configuration
  • Syncornize or Reimport
  • Delete all the IntellJ related files like .idea and reimport project
  • remove all the dependency files and then run mvn clean package
  • Switch Java version or use embedded Java in IntellJ
  • run mvn idea:idea
  • Change Maven Home
  • mark src directory as source in the module tab

The last thing I did worked: Delete the .idea and .iml in the project, delete all the dependency files and then delete the IntellJ from the computer. After reinstalled the IntellJ my project built successfully. I wish I could have a better way to solve this.

0
votes

I had the same problem. I've changed maven version from 3.0.5 to 3.0.4 in Idea settings and all works fine now. Don't know why that helps me.

0
votes

I tried invalidating cache, changing the Maven to installed version and nothing worked.

Closing and recreating a new project resolved it.

0
votes

I closed the project and imported it again by clicking on the root pom (not just the folder, but the pom file itself).

0
votes

I tried everything above with no joy. However I did one thing that finally got it to work:

I went to C:\Users\.IntellijJIdea2018.2 and just deleted the entire folder.

It removes all the settings and cache for IntelliJ. I had to reimport my project from scratch but a simple remove and reimport hadn't worked before, but this finally got it working again.

0
votes

Delete the .idea folder and close the IDE

open the IDE again and import the project which will do a fresh import because .IDEA folder is deleted by us earlier

Check the external libraries module and if it is not populated with the required dependencies then check if the maven settings.xml location is given correctly in the IDE

0
votes

There is also a possibility which was not mentioned. If you import library from com.sun.*. It will also cause this problem.

Programs works when run in ide, cause these classes in com.sun.* are all in jre/lib directory, it will be loaded when running. But when you run mvn package, these libraries won't be accessible because of the restriction of oracle since java 1.6(these libraries was deprecated in a way). To solve this problem, you can add

<build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.3.2</version>
                <configuration>
                    <source>1.8</source>
                    <target>1.8</target>
                    <encoding>UTF-8</encoding>
                    <compilerArguments>
                        <verbose />
                        <bootclasspath>C:/Program Files/Java/jdk1.8.0_161/jre/lib/rt.jar</bootclasspath>
                    </compilerArguments>
                </configuration>
            </plugin>
        </plugins>
    </build>

remember to replace the cootclasspath with you own path of rt.jar

You can search Access restriction: The type XXX is not accessible due to restriction on required library for more detail.

0
votes

If there are erroneous modules configured them do these steps:

  • Go to Project Settings
  • Go to Modules
  • Delete modules that should not be there
0
votes
  1. From maven tab click + and choose pom.xml
  2. From maven tab click download sources and documentation
  3. On project structure(where you can view project files/directories) right click the project you're trying to build and choose Build Module Project Name.
  4. From tab Run- Edit Configurations with + add Application and fill the below fields: i. Main Class- Manually choose from Project tab select the main class ii. Use classpath of module - choose the application name iii. Shorten command line - classpath file
  5. Now simply run the app.
0
votes

In my case the problem was in different Project Java SDK version. When I was building project from terminal, maven used Java 8, and when I was building from IDEA, it used Java 11.

Go to File > Project Structure... and in Project Settings set Project SDK to the version you need.

0
votes

For me the problem was that I had Ajc compiler selected in the IntelliJ Java Compiler settings. Once I changed it back to Javac everything worked fine.

0
votes

For me in Mac, I solved it by deleting the Intellij Idea Appication from my computer and deleting the cache files in ~/Library/Application Support/JetBrains/IntelliJIdea2020.1 ~/Library/Caches/JetBrains/IntelliJIdea2020.1

Then re-install it, open my project, and build it successfully!

0
votes

Another reason for this error is usage of dependencies such as lombok in pom.xml file. If you are using lombok annotations such as @Data in the java file, then you need to install lombok plugin in intellij to get rid of "Errors" in IDE.

0
votes

I also was getting the same problem. From terminal using maven command (mvn clean install -DskipTests=true) project was built successfully. But in intellij it was unable to identify the jar spring library files.

Fixed it using the following steps:

  1. close your IDE(intellij)
  2. delete sudo "rm -rf /<your_project_location>/.idea/" (/home/user/projects/test_proj/.idea/)
  3. open your IDE again. It will reindex your files and issue will be resolved

RCA: I suspect it happens due to permission issue in linux