Why does IntelliJ give me "Package doesn't exist" error?
Asked Answered
P

40

272

I'm trying to use the barbecue barcode printing library. I have successfully added the library to IntelliJ through project structure add library. Then I imported the packages and wrote the methods, which gave me no error. The packages were available in the class.

But when I compile it gives me the error:

error: package net.sourceforge.barbecue does not exist

How can this be?

I'm coding in ubuntu, is there any other place to which I have to add the library?

Polychromatic answered 22/11, 2013 at 4:28 Comment(5)
And you're certain that this JAR is in the Libraries section of your Project Structure?Oblique
Verify that the scope of the library (in the project structure window) is Compile. If set to a scope of Provided it will cause the behavior you describe.Koh
If you have a dependency under a maven profile, make sure you select the correct profile in the maven tree "Profiles", when you compile the project.Mono
If you are using Gradle for your project check this response : https://mcmap.net/q/53429/-correct-way-to-add-external-jars-lib-jar-to-an-intellij-idea-projectNotification
This solution worked for me. Follow the given linkToluol
C
248

Just reimport didn't work. Following worked for me.

File -> Invalidate Caches /Restart

Then

Build -> Rebuild Project

That will reimport maven project.

Note : You need to invalidate the cache AND ALSO rebuild the project.

Canst answered 16/3, 2017 at 8:53 Comment(4)
Worked like a charm but can you also explain why does it happen?Orlan
Okay, just for anyone else viewing this answer -> Note that you need to invalidate the cache AND ALSO rebuild the project. I used my intuition and did only the first part, because I do see IDEA "rebuilding" and indexing after I restart, but I don't think that is enough. You need to explicitly rebuild the project.Liqueur
@Raj Rajeshwar Singh Rathore it's because maven (or gradle, if you use gradle) remembers / caches parts of the previous build to then build faster each time you ask it to build your project. So when you first get the error maven remembers that this module was missing.Nankeen
I also removed all .iml files from project recursively, then rebuild project. And all has been ok.Trelliswork
A
124

I tried to "Maven > Reimport" but the only thing that actually fixed it was to close the project, delete the .idea directory, and reopen the project.

Autostability answered 2/6, 2016 at 19:59 Comment(9)
This helps but the problem appears again after some time.Carp
I had similar issues with IntelliJ 2018 and Gradle. It couldn't find Spring packages. Doing this fixed the issue for me.Good
To reimport: Press Ctrl+Shift+A to find actions, and input "reimport", you will find the "Reimport All Maven Projects".Erethism
Eureka, finally something that works! All the reimports in the world weren't fixing it. Not even "invalidate cache and restart", but this did...Glister
I think it's "Reload All Maven Projects" now. It also worked for me when invalidating cache and rebuilding didn't do anything.Skardol
If you have Maven profiles, make sure that you are enabling the right ones if needed. After enabling/disabling profiles reload all Maven projects.Meijer
I suggest making sure that all pom.xml files in the project are added or recognized as Maven Projects by IntelliJ. The file icon should be a small m. If not, right click the pom.xml file, and choose Add as a Maven ProjectMeijer
for me it was sufficient to delete the .idea/libraries folderNeurasthenia
I tried: (a) Invalidate cache and restart. (b) Invalidate cache with all the optional options checked. (c) rebuild the project. (d) ./gradle clean build (project built fine) (e) restart IntelliJ Idea. The only solution that worked for me was this one, deleting the .idea folder with the IDE closed, and then rebuilding the project.Ciaphus
H
71

None of the 13 existing answers worked for me. However, I could resolve the issue by first removing all modules:

  1. open File > Project Structure...,
  2. go to Modules tab,
  3. select all modules and press the remove button,

then removing all remaining Maven modules from Maven tool window:

  1. select all modules,
  2. right click on them,
  3. press Remove projects,

and then adding them again in Project tool window:

  1. right click on root pom.xml,
  2. press Add as Maven project,

now unignoring any ignored modules from Maven tool window:

  1. select all ignored (grey) Maven modules,
  2. right click on them,
  3. press Unignore,

and finally rebuilding using Build > Rebuild project. This assumes that a mvn clean install already happened.

Hienhieracosphinx answered 6/6, 2019 at 7:54 Comment(10)
Worked on IntelliJ Ultimate 2019.1.2! Invalidating Caches didn't work.Reimporting the project didn't work. This solution did!Sweyn
Just tested on 2019.1.3 and yes, this is a working solutionSeamount
Works for version 2019.3!Sparhawk
Works for version 2020.2 as well. Was pulling my hair out until I found this!Kudu
Thank you! Somehow, some way, this worked for me in 2020.1.4. Shouldn't have to worry about IntelliJ breaking so much in their updates, but 2020 has been a nightmare. Thanks for sharing this fix.Oliy
Worked for me after updating to 2021.1Polygenesis
I have no idea why this worked, but it did! Thanks! IDEA version 2022.1.2Wynd
This right here! IntelliJ 2021.2.3 And it worked like a charm! I should note that I was messing with this project's structure before this problem started occurring. I was added a module then removed it.Misdate
I had a single failing module in a project with 14 modules. I deleted the problem module and re-added it and -- it worked! Thanks for the inspiration.Wooton
Works for 2024.1 ! ThanksPallbearer
B
54

Right click your project / Maven (at bottom) / Reimport

Edit, much later: I also saw this happen much more frequently when I had the Clover plugin installed. Drop that plugin like a bad habit!

Beadle answered 4/8, 2015 at 20:24 Comment(1)
In newer versions (mine 2022.1.2) of IntelliJ, there is a Reload Project position instead of Reimport.Intrados
T
47

In my case the only thing that worked is:

mvn idea:idea

The good thing is that you don't have to delete .idea folder or .iml files and loose all configuration. Everything will be preserved.

(Possibly something like gradle idea works for gradle too).

Triglyph answered 10/5, 2020 at 18:13 Comment(1)
Though it temporarily solved my issue and I upvoted, I later discovered that command is obsolate and can cause problems. The official page for the plugins usage states Apache Maven IDEA Plugin (RETIRED). maven.apache.org/plugins/maven-idea-plugin/usage.htmlMedan
P
27
menu -> build -> Rebuild Project

has worked for me

(Invalidating caches without this step doesn't help)

Phylactery answered 23/3, 2018 at 22:42 Comment(1)
Same thing helped me - Right click on project -> Rebuild Module <module-name>Abase
O
19

I did re-import all maven projects. This worked for me.enter image description here

Overspend answered 13/8, 2019 at 5:17 Comment(1)
This one worked for me after trying a lot from the other suggestions.Hamon
V
15

If you added a library to the project structure (rather than via maven, that would be different), be sure it is included as a dependency for the relevant module.

Project Structure -> Modules -> Dependencies

Verney answered 22/11, 2013 at 19:34 Comment(0)
S
12

It's a very annoying problem which happens quite often. Especially after switching to a different git branch. It wasted me way too much time to troubleshoot this kind problem. I have tried all the methods above. But I can't find a reliable way. Here I just summarize those steps which could help in my situation. Jetbrains, please fix this issue to save your customer's precious time.

  1. Make sure do a success command line build (If UT failed, please ignore UT by using -Dmaven.test.skip=true.
  2. In the "Maven Projects" view, try to use "reimport" all the maven project.
  3. In the file menu, use "Invalidate Caches"
  4. Delete .idea folder, basically create the workspace from scratch. (That's the only reliable way can solve this issue)
Stipend answered 19/11, 2018 at 22:16 Comment(4)
Tried all of these and the only thing that worked for me was #4, closing IntelliJ, deleting the .idea folder, and reloading the project. This happened to me after creating a new git branch.Prevalent
sounds like a bug with intellij, I wonder if there is issue created for that?Idiot
Agree, happens to me when any git-related action is performed outside of IntelliJ. Meanwhile, it builds for me just fine, happens only when I'm doing Build > Recompile '<SomeClass.java>' for hot swap. Hence, none of the solutions like "Open/close IntelliJ", "invalidate/rebuild project" and so on, acceptable for me. But it pisses me off seriously.Honeymoon
Deleting the .idea folder is the only way worked for me usually, but the problem is then that I lose a lot of other stuff with that as wellVedavedalia
S
11

In my case the problem was that there was a different repository directory configuration in IntelliJ and in settings.xml file.

Check both repository directories are the same:

IntelliJ (File > Settings > Build,Execution,Deployment > Build Tools > Maven )

IntelliJ Local Repository Configuration

settings.xml (usually in C:\Users\myuser\.m2 or /home/myuser/.m2)

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">

  ...
  <localRepository>C:\Users\myuser\.m2\repository</localRepository>
  ...
</settings>

After fixing directories run:

  1. Generate Folders and Update Sources for All Projects

enter image description here

  1. Reimport all maven projects

enter image description here

Stash answered 16/9, 2020 at 9:9 Comment(1)
Adding the localRepository line in my settings.xml fixed the issue for me. I use Intellij IDEA 2021.1 Community Edition Build#IC-211.6693.111Orji
D
10

Tried all the above approaches, didn't work. Finally running maven clean install solved it!

Drona answered 4/10, 2017 at 10:1 Comment(1)
Crazy, but this one actually worked for me... even though org.mapstruct (1.5.1-FINAL) was everywhere in the lists, it simply wouldn't use it to build. mvn clean install actually worked...Argyrol
T
9

Quit IntelliJ, remove every .idea directory:

rm -Rf **/.idea/ 

and restart.

Tenorrhaphy answered 19/3, 2018 at 10:12 Comment(3)
This helped for Community Edition 2017.2. I also had to import gradle project after this. 2017 and this problem still occurs.Bivalent
If your project is simple JAVA project and not Maven project then Don't do this before actually looking at the list of dependencies in : File>Project Structure>Modules>Dependencies. Else you will lose the list of dependencies you would actually need. As one method to solve this issue is by downloading all the Jars listed at above location.Arianearianie
I did this in addition to removing any *.iml files in the source directories to remedy the problem. It doesn't appear that IntelliJ created any new *.iml files for me.Tangier
F
6

Invalidate Caches/ Restart and then Build -> Rebuild Project helped for me

Familial answered 25/6, 2018 at 8:40 Comment(1)
It doesn't helpVedavedalia
S
6

I tried all appreciated answers and none of them solve my problem!

According to Intellij community, there is a bug with Maven builds in 2020.1 and 2020.1.1 versions: https://youtrack.jetbrains.com/issue/IDEA-237320?_ga=2.235486722.203129946.1591253608-322129264.1584010541

Please try to run on 2019.3.4 version (Its worked for me from the first time)

You can download from here

https://www.jetbrains.com/idea/download/previous.html?_ga=2.190043688.203129946.1591253608-322129264.1584010541

Saintebeuve answered 4/6, 2020 at 7:27 Comment(1)
This workaround about path.macros.xml file has helped me: youtrack.jetbrains.com/issue/… 2020.1 works now.Hepcat
I
5

Similar to cvdr. Too high a Java version can be the problem.

A collegaue just have this problem with multiple java sources in our test project. She had just updated to a later Intellij and when we investigated none of the rebuild options worked but Intellij seemed to have 'bumped' the project Java settings to Java 11 (I guess it takes highest installed version on upgrade install?) Setting it back to Java8 and the project compiles successfully.

Go File>Project Structure > Project Settings > Project and select the right ones in the drop downs.

Intrusion answered 8/7, 2021 at 15:58 Comment(0)
F
5

I got this error after I changed pom, and I fixed it by execute:

mvn idea:module

it works for me

Formulary answered 23/11, 2021 at 1:30 Comment(0)
I
4

Here is a solution worked for me: Disable the "Use --release option for cross-compilation like the following in intellij idea: got Settings -> Build,Execution,Deployment -> Compiler -> Java Compiler and disable:

Use '--release' option for cross compilation(java 9 and later)

Incontrollable answered 25/5, 2019 at 9:35 Comment(0)
C
3

As someone who only occasionally needs to do Java work, this was very annoying. Inevitably, packages would have been added since the last time I ran our server inside IntelliJ and it would fail to build. I found what seems to be an easier solution: just don't build within IntelliJ. Build from the command line via Maven, then make sure that the run configuration does not list Build as a "Before launch" task.

Corral answered 15/10, 2018 at 17:29 Comment(0)
M
3

I tried

  1. "Maven > Reimport"
  2. Deleting the .idea directory, and reopening the project.
  3. File -> Invalidate Caches/Restart then Build -> Rebuild Project
  4. Deleting what is inside local .m2 folder, and downloading dependencies again.
  5. Running mvn idea:idea in Maven console (Though this command is obsolete, I had to try.)

in different combinations.

But going from Intellij 2020 version to 2019 solved my issue.

Medan answered 17/8, 2020 at 5:2 Comment(3)
I tried with intellij 2019 but still issue is not resolved any other suggestions.?Hatband
Sorry, but it has been a long time since I faced this error and the solution was a result of trial and error. So I don't have anything else than try everything listed here.Medan
no problem thanks for replying Onat Korucu .Hatband
D
3

I had this problem in IntelliJ 2020.3 and tried the invalidate cache option and rebuild, but the problem persisted. The only thing that fixed it was to rename the package and rename it back to what it was originally.

Daglock answered 8/4, 2021 at 14:46 Comment(0)
I
2

I had the same problem and it was fixed for me by changing the "Maven home directory" in Settings from "Bundled" to my locally installed maven. Perhaps this triggered some kind of refresh somewhere since I had not changed this setting for months without any issue.

Implicative answered 12/3, 2018 at 14:33 Comment(0)
S
2

What happens here is the particular package is not available in the cache. Resetting will help solve the problem.

  1. File -> Invalidate Caches /Restart
  2. Goto terminal and build the project again

    ./gradlew build
    

This should download all the missing packages again

Somali answered 14/8, 2019 at 5:43 Comment(0)
E
2

If you are trying the suggested ways and still no chance, be sure about your order:

  1. Delete your .idea/
  2. Invalidate and Restart Cache afterwards
  3. Import maven projects from your maven tool

If you did not invalidate and restart cache just after deleting your .idea/, Intellij keeps generating it and that was keeping error in my case.

Esp answered 15/6, 2020 at 10:36 Comment(0)
W
2

I had the same issue with my unit tests. I created tests on my master branch and early everything worked well, no matter what branch I was using. But when I switched again to master branch, tests did not work anymore. What helped me was to:

close intellij -> delete .idea file from directory -> open project again by pom.xml (idk if it matters what way you open the project, but first time when I tried to open it normally by intellij, it still dit not work) -> reload all maven projects from right menu -> rebuild project and that's it, everything works now

Wame answered 18/3, 2021 at 9:38 Comment(0)
M
1

I had the same problem. I fixed it by applying the android-apt plugin https://bitbucket.org/hvisser/android-apt

Mauceri answered 26/12, 2014 at 3:23 Comment(1)
It says repository is moved to github.com/littlerobots/android-aptMedan
P
1

Maven reimport, rebuild and invalidate caches did not work. I solved it by opening a terminal and executing maven clean install in the root folder project. (IntelliJ was opened and I was able to see the IDE updating and triggering reindexation while maven was doing his job)

Parenteral answered 28/4, 2020 at 12:12 Comment(0)
M
1

The above solutions didn't work for me. I had to add the dependency explicitly in the pom.xml.

Just add your jar under resources/library and then add it as a dependency in your pom.xml like:

        <dependency>
            <groupId>your-jar-group-id</groupId>
            <artifactId>artifact-id</artifactId>
            <version>1.0</version>
            <scope>system</scope>
            <systemPath>${basedir}/src/main/resources/library/name-of-jar.jar</systemPath>
        </dependency>

Try this out if none of the above work.

Mcginley answered 22/7, 2021 at 17:29 Comment(2)
I am using intelliJ community edition. I have a jar file that contains class definitions from a project, that I need available in a workspace I use for "Scratch" experimental work. I included the jar file in "Project Structure" > "Modules" > "Dependencies", and that has worked for me in the past. But it keeps saying "cannot find package XYZ" as if it cant locate one of these class definitions that is referenced by an import statement. I tried everything above short of deleting the .idea folder. Your solution worked for me, much thanks.Iong
It turned out that the path had to be relative, because I was storing the jar file somewhere else in my file structure, not located in the project workspace: <systemPath>${basedir}/../../lib-for-jars/classdefs-1.0.jar</systemPath>Iong
M
1
  1. Delete your .idea/
  2. Invalidate and Restart Cache afterwards
  3. Re-import project
Midships answered 9/12, 2022 at 6:5 Comment(0)
U
1

I solved this problem by updating my local JDK 17 to oracle JDK 17.0.7.

I can't remember which distribution I was using.

Unsought answered 1/5, 2023 at 16:8 Comment(0)
B
0

If you do not want to destroy .idea, you can try :

  • open Project Structure > Modules
  • unmark the java folder as a source folder
  • apply / rebuild
  • then mark it again as a source folder
  • rebuild
Berneta answered 26/5, 2020 at 18:54 Comment(0)
O
0

In case you're facing very weird "unable to resolve java, sun packages problem", try the following:

  1. Open Project Structure and change Project SDK to another version, example: java 8 -> 9; 11->13, etc, and wait until it re-index all jdk's jars. Switch between jdks with same version may not work! (Ex: jetbrains jdk11 -> openjdk 11)
  2. Open a new project (or create a empty one); pause new project's indexing; close the old one; start indexing; open the old project and pause the new project's indexing and wait.
Oma answered 9/6, 2020 at 11:27 Comment(0)
G
0

I tried compile a java 8 project with JDK 12 and has the same issue. None of previous answer solved my problem.

I changed o Shortel Command Line to "JAR Manifest" and worked like a charm.

intellij

Goodkin answered 16/6, 2020 at 19:46 Comment(0)
C
0

Follow the steps below:

  1. Ctrl+Shift -> Type Invalidate Caches -> Chech all options except: Ask before...
  2. Superior menu -> Build -> Rebuild Project
Calumny answered 19/3, 2022 at 21:24 Comment(0)
F
0

I created two new classes under a new package and used it in rest of the code, Intellij was able to resolve these no red highlights were shown in the intellij editor. While building it was showing package doesn't exist error. I tried everything from gradle clean build, rebuild project, clear .idea and .gradle and reimporting the project, clearing the gradle local cache but nothing was working. Finally I refactored the name of the new package and this time intellij was able to recognize the new classes and it started working.

Franklyn answered 7/4, 2022 at 8:16 Comment(1)
This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From ReviewSocietal
H
0

Invalidate caches worked for me but it's too long to recover the caches so I don't have the patience to wait for it. I found another way to solve it in my case. "Repair IDE" step 3 (delete Package search project caches) worked for me perfectly

enter image description here

Heterochromosome answered 10/5, 2022 at 8:38 Comment(0)
W
0
package com.example;

import com.sun.jna.Library;
import com.sun.jna.Native;

public class C {
    public interface Kernel32 extends Library {
        public void OutputDebugStringA(String Text);
        public void DebugBreak();
        public void Sleep(int a);
    }

    public static int incint(int in1)
    {
        testpkg.xxxBird.Say("xxxee"); //only use this statement to call external lib
                                      //I don't use "import" statement.
        return in1*2;
    }
}

I am using intellij idea. You need to add testpkg path in project dependency. enter image description here

Weltschmerz answered 22/9, 2022 at 14:59 Comment(0)
I
0

I faced the same situation in ver 2022.1.4. I tried all solutions from the first answer, nothing worked except the delete the ".idea" folder. Even through many friends mentioned this solution, I couldn't find this folder, I was looking around user profile and AppData folders. This folder was in fact created under the project folder itself.

I closed the project, and re-opened after deleting this folder.. everything back to normal. It felt like the "Intel" was lost and the IDE was only "lij" for sometime.. lol

Indebtedness answered 21/11, 2022 at 13:3 Comment(0)
S
0

I tried all answers, but eventually what helped me was changing the Maven from bundled to my own Maven distribution.

I think vice versa (changing from own to bundled) will help as well.

enter image description here

Samphire answered 19/1, 2023 at 14:36 Comment(0)
Y
0

For me, to simply quit IntelliJ and reopen it was enough to get beyond this error.

Yukyukaghir answered 10/10, 2023 at 3:44 Comment(0)
Q
0

I don't know if this may help but I've tried all of the solutions mentioned here and more. NOTHING SEEMS TO WORK.

I even look every related issues raised on github issues in Jetbrains and Nothing.

And I was about to loose my mind and started pulling out my hairs and something cames out to my mind.

What I did was use a <dependencyManagement> </dependencyManagement> on my project and specify all the versions and everything then mvn clean install and then on another project I added the dependency as we normally do then IntelliJ, Vscode, started to recogize my imports and classes.

I hope it will also work for you.

Quennie answered 15/4 at 17:20 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.