The declared package does not match the expected package ""

Question

I am using Eclipse and have not used Java for sometime. However, I can compile my code on the command-line just fine and generate the necessary .class files. In Eclipse, it complains that The declared package "Devices" does not match the expected package "". What does this mean and how can I fix it?

Sample code:

package Devices;

public final class DevFrequency 
{
    public short messageID;
    public double frequency;
    public short converterID;
    public DevFrequency() 
    {
    }
    public DevFrequency(short _messageID,double _frequency,short _converterID)
    {
        messageID = _messageID;
        frequency = _frequency;
        converterID = _converterID;
    }
}

The name of my project is DeviceDDS.

If you're going to change your question retrospectively (which seems pointless, to be honest) you need to be consistent about it - you haven't edited the first paragraph of the question. You've also made all the comments look odd. Why change everything, nearly a year and a half later? — Jon Skeet, Jan 18 '13 at 13:47
In my case (using VSCode Java Project Manager extension), for some reasons, I had to manually change the class' package, or you could hold the mouse pointer on the red line beneath the error and then hit "quick fix" to do it automatically. (Of course I have no idea how this happened because the VSCode Java Project Manager handles this when you create a new folder, on its own and I couldn't replicate this behavior once again). Anyways. — aderchox, Feb 17 '21 at 08:48

candied_orange · Answer 1 · 2018-04-26T18:48:35.157

177

Try closing and re-opening the file.

It is possible to get this error in eclipse when there is absolutely nothing wrong with the file location or package declaration. Try that before spending a lot of time trying these other solutions. Sometimes eclipse just gets confused. It's worked for me on a number of occasions. I credit the idea to Joshua Goldberg.

edited Apr 26 '18 at 18:48

answered Aug 09 '14 at 16:06

candied_orange

7,036
2
28
62

5

Had this problem with a Gradle project inside VS Code. Re-open fixed it. – TastyWheat Sep 18 '18 at 19:46
2

opening and closing the file in the eclipse editor helped solving the issue. I had added a source folder in java config build - source tab, the error did not removed, but when I closed and opened the editor in eclipse, it helped . :-) – JassJava Aug 09 '20 at 08:29
1

Exiting and restarting eclipse fixed the problem too. – Don Smith Sep 22 '20 at 18:23
2

he he .. I spent an hour trying to fix it and then saw this. – Vikash Oct 22 '20 at 12:35
@candied_orange Thank you. closing and opening the file multiple times fixed it for me as well – raikumardipak Dec 17 '20 at 04:06
1

It happened to me with Vim and CoC and coc-java LSP after I moved some stuff around. Restarting vim solved the problem. – Fernando Basso Mar 25 '21 at 16:36
ha ha wasn't expecting this to work for me, thanks btw. – Ananthu K Kumar Jun 30 '22 at 09:16
@candied_orange Good idea to try closing and reopening the file. It looks like this worked for a lot of people. But it did not work for me. – Brian Schack Oct 04 '22 at 14:15
I hate that this was the solution – ojchase Apr 17 '23 at 20:01

score 66 · Accepted Answer · edited Jan 18 '13 at 13:44

66

Eclipse expects the declared package to match the directory hierarchy - so it's expecting your Java file to be in a directory called "Devices" under your source root. At the moment it looks like the file is directly in your source root. So create the appropriate directory, and move the file in there.

Note that conventionally, packages are in lower case and include your organization name in reverse DNS order, e.g.

com.foo.devices;

edited Jan 18 '13 at 13:44

answered Aug 09 '11 at 14:13

Jon Skeet

1,421,763
867
9,128
9,194

3

@Sakti: You can't as far as I'm aware, and I'd strongly advise you not to even if you could. *All* experienced Java developers will expect you to follow the normal conventions. – Jon Skeet Apr 17 '12 at 18:15

nanospeck · Answer 3 · 2013-08-19T08:53:56.733

49

Solution 1 : One solution that worked for me when this error "The declared package does not match the expected package" occured for a project I checked-out from eclipse CVS :

1.Right click the project in the navigation bar and click 'delete'
2.Make sure 'Delete project contents on disk' option is NOT checked, and click OK.
3.Now after the project is deleted, go to File -> Import -> General -> Existing Projects into Workspace
4.Select your workspace from the directory listing and check the box next to your project name. Click 'Finish'

Solution 2 : Once again I got this error with the following message

Eclipse build errors - java.lang.Object cannot be resolved I had to follow another route mention here and the error went away.

In the mean time, the work around is to remove the JRE System Library from the project and then add it back again. Here are the steps:

Go to properties of project with the build error (right click > Properties) View the "Libraries" tab in the "Build Path" section Find the "JRE System Library" in the list (if this is missing then this error message is not an eclipse bug but a mis-configured project)
Remove the "JRE System Library"
Hit "Add Library ...", Select "JRE System Library" and add the appropriate JRE for the project (eg. 'Workspace default JRE')
Hit "Finish" in the library selection and "OK" in the project properties and then wait for the re-build of the project

Hopefully the error will be resolved ...

edited Aug 19 '13 at 08:53

answered Aug 24 '12 at 13:30

nanospeck

3,388
3
36
45

I had to do this too (adding a directory of groovy tests to the build). Don't forget to make notes on your run configurations, which you'll need to recreate. Any idea why this is needed? Such a pain. – Joshua Goldberg Mar 14 '13 at 14:56
11

Simpler solution: I was in this situation again, and was able to get it working by closing the project, restarting Eclipse, and re-opening the project. – Joshua Goldberg Mar 19 '13 at 15:02
12

Even simpler! I just had it again, and it went away by closing and re-opening the single problematic file's editor. – Joshua Goldberg Apr 17 '13 at 16:38
4

Restarting eclipse seems to fix it. – Mike R Sep 06 '13 at 15:49
Solution 1 worked for me. Very weird. I have imported the same git clone into Eclipse on other machines and not seen this problem. – dnuttle Feb 24 '14 at 14:55
This issue is still present in Eclipse Luna, where none of these two solutions functions. However, [the restart suggested by Joshua Goldberg](http://stackoverflow.com/questions/6997524/the-declared-package-does-not-match-the-expected-package#comment21950896_12110407) does it. – Luís de Sousa Mar 03 '15 at 20:03
Solution #2 is pathetic :D "have you tried turning it on and off, again?" – Gewure Dec 22 '16 at 09:41
Solution 1 worked. This is funny but it worked perfectly – Manish Mudgal Oct 03 '18 at 12:26
The first solution worked for me. Just wondering somebody can detail out why it happens as such? – Dhamo Dec 09 '18 at 05:34
Solution 2 worked for me. Thanks a lot. You saved me smashing up my laptop. – Othello May 02 '20 at 18:05
Sol #1 is worked for me. thanks lot – Maddy Dec 26 '21 at 16:47

score 17 · Answer 4 · edited Mar 31 '15 at 21:01

17

I resolved the problem by following these steps:

Select the project - Right click - java build path.
In source tab - you change the src to src/main/java.
Eclipse will reorder all the project.

edited Mar 31 '15 at 21:01

ZygD

22,092
39
79
102

answered Mar 31 '15 at 20:13

dafali

171
1
2

score 12 · Answer 5 · edited Jun 19 '13 at 12:34

12

I had this problem - the other classes within my package were fine, but one class had the error against it. There was nothing wrong with the package declaration.

I fixed it by doing refactor->move and moved the class to another package temporarily, then refactor->move back to the original package.

edited Jun 19 '13 at 12:34

fedorqui

275,237
103
548
598

answered Jun 11 '13 at 10:11

ayahuasca

556
10
9

score 4 · Answer 6 · answered Dec 11 '20 at 22:12

4

I fix it just changing the name to lowercase and now Eclipse recognizes the package.

answered Dec 11 '20 at 22:12

Alejandro Garcia

175
1
3

It worked for VSCode too, thanks. but why exactly this was throwing error, and How this First_char_capitalization made it work? could you please tell? – GD- Ganesh Deshmukh Jul 18 '21 at 15:51

score 2 · Answer 7 · answered Jan 28 '20 at 08:12

This problem got resolved by mentioning the package name

I moved my file Test_Steps.java which was under package stepDefinition

by just adding the package stepDefinition the problem got resolved

So this problem can occur when you have a package and you are not using in your class file.

Adding it has resolved the problem and the error was no longer appearing.

score 2 · Answer 8 · edited Jan 18 '13 at 13:44

2

Create a new package under your project called "Devices" and place your class in it. This is equivalent to the class being placed in a directory called "Devices" in your project source folder.

edited Jan 18 '13 at 13:44

answered Aug 09 '11 at 14:14

tskuzzy

35,812
14
73
140

score 2 · Answer 9 · edited Jan 18 '13 at 13:44

2

You need to have the class inside a folder Devices.

edited Jan 18 '13 at 13:44

answered Aug 09 '11 at 14:14

Marcelo

11,218
1
37
51

score 1 · Answer 10 · answered Feb 18 '13 at 12:47

1

Make sure that Devices is defined as a source folder in the project properties.

answered Feb 18 '13 at 12:47

Adam Matan

128,757
147
397
562

score 1 · Answer 11 · answered Jul 18 '14 at 07:33

1

Got the same kind of error but my package was absolutely correct. When I just closed and opened my editor, the error disappears. Hope this might help in some scenarios.

answered Jul 18 '14 at 07:33

Easwaramoorthy Kanagaraj

3,925
8
36
62

score 1 · Answer 12 · answered Mar 11 '17 at 16:56

I fixed this by removing an "excluding" attribute for that package in my .classpath file. Remove the attribute, not the whole tag, or "src/java" will cease to be a source folder.

<classpathentry excluding="com/myproject/mypackage/mysubpackage/" kind="src" path="src/java"/>

score 0 · Answer 13 · answered Feb 12 '14 at 10:01

0

Make sure that You have created a correct package.You might get a chance to create folder instead of package

answered Feb 12 '14 at 10:01

Karthick

1

score 0 · Answer 14 · answered Aug 11 '14 at 14:57

0

Create directory [your.project.name] in workspace root directory of your project.
Copy *.java from "src" to that directory.
Close and reopen project.

answered Aug 11 '14 at 14:57

B347tl7

1
1

score 0 · Answer 15 · answered Sep 16 '14 at 16:23

This happened to me when I was checking out a project from an svn repository in eclipse. There were jar files in my .m2 folder that eclipse wasn't looking at. To fix the issue I did:

right click project folder Configure > Convert to Maven Project

and that solved the issue.

score 0 · Answer 16 · answered Feb 11 '15 at 20:16

0

There are a million answers, but here's another one: copy the files into a new package, delete the old package and rename the new package to the old package's name.

answered Feb 11 '15 at 20:16

Omri374

2,555
3
26
40

score 0 · Answer 17 · answered Oct 08 '15 at 10:02

0

Make sure you are not using default package. Create a new package with name 'devices' and copy this code inside it and use.

answered Oct 08 '15 at 10:02

score 0 · Answer 18 · answered Jul 12 '16 at 20:56

0

I had have this sort situations when I copied classes from other packages/projects.

Menu->Project->Clean usually helps.

answered Jul 12 '16 at 20:56

Yuriy N.

4,936
2
38
31

score 0 · Answer 19 · answered Dec 10 '16 at 17:27

0

In my case I selected the error marker in the Problems tab and deleted it since the Java's file main method was being executed correctly. That is some glitch in Eclipse Neon with the multitude of plugins it has installed.

answered Dec 10 '16 at 17:27

Leniel Maccaferri

100,159
46
371
480

score 0 · Answer 20 · answered Jan 18 '19 at 20:39

I faced this issue too when I had imported an existing project to eclipse. It was a gradle project, but while importing I imported it as regular project by clicking General-> Existing Projects into Workspace. To resolve the issue I've added Gradle nature to the project by :::: Right click on Project folder -> Configure-> Add Gradle Nature

score 0 · Answer 21 · answered Dec 09 '19 at 17:08

0

I was using Spring Tool Suite 4. Not able to figure out the issue. The directory structure was according to the package name.

But cleaning the project helped me.

answered Dec 09 '19 at 17:08

prisar

3,041
2
26
27

score 0 · Answer 22 · answered Oct 23 '20 at 07:02

I had the same issue with a maven project in Eclipse IDE. I was able to resolve it by replacing the .classpath file with the correct format. After replacing close and open the project.

Sample .classpath file

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" output="target/classes" path="src/main/java">
        <attributes>
            <attribute name="optional" value="true"/>
            <attribute name="maven.pomderived" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry excluding="**" kind="src" output="target/classes" path="src/main/resources">
        <attributes>
            <attribute name="maven.pomderived" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry excluding="**" kind="src" output="target/classes" path="src/main/webapp">
        <attributes>
            <attribute name="maven.pomderived" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry kind="src" output="target/test-classes" path="src/test/java">
        <attributes>
            <attribute name="optional" value="true"/>
            <attribute name="maven.pomderived" value="true"/>
            <attribute name="test" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8">
        <attributes>
            <attribute name="maven.pomderived" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
        <attributes>
            <attribute name="maven.pomderived" value="true"/>
        </attributes>
    </classpathentry>
    <classpathentry kind="output" path="target/classes"/>
</classpath>

score 0 · Answer 23 · answered Jun 11 '21 at 17:50

you might want to check your Java 'build path' in the project properties, if the 'source' directory (path) is not properly setup in there, then this will cause this error to occur for all the classes therein.

So the path must specify the 'root' (containing) directory in which the sources within the package exists ...

score 0 · Answer 24 · answered Oct 06 '22 at 11:21

0

Another thing that we can do is On the error, ctrl+enter and move the file to the expected package

answered Oct 06 '22 at 11:21

Shash

19
2

score 0 · Answer 25 · answered Feb 03 '23 at 11:53

In my case being used gradle, it happend due to wrong name in settings.gradle. Rename rootProject.name = 'somename' to actual name of your project folder. Cleanup it all with topbar->project->clean....

And you are done my friend!

(Also I've reset values in build.gradle to latest versions but that just for case)

The declared package does not match the expected package ""

25 Answers25

Linked

Related