The import cannot be resolved in eclipse

Question

Though I have all my source in proper packages.It couldn't find at the time of Building Project.Normally it shows links everything.But at the time of Build Project or Autobuild while directly running project.

The import ecnet.rd.config cannot be resolved

like it shows for all the internal imports.But external imports like imports from JAR files are working.

P.S :

My Eclipse latestly crashed but it was working well after that, Once again this kind of things are happening.

Please help to find the way to solve this.

m0skit0 · Accepted Answer · 2015-08-11T15:32:14.097

42

In my experience, it is usual with Eclipse to have the build messed up. Make sure Build automatically is checked and Clean. If it doesn't work, restart Eclipse and do again.

Also as Tech Junkie comments below, try also Clean all projects.

edited Aug 11 '15 at 15:32

answered Feb 03 '14 at 12:53

m0skit0

25,268
11
79
127

2

it will be helpful for newbies...... – sunleo Feb 03 '14 at 13:05
4

worked when I said, 'Clean all projects' – Venkatesh Laguduva Oct 25 '14 at 12:43
++ for @TechJunkie's comment - worked for me, whereas cleaning the problematic project alone didn't (for some odd reason). – Priidu Neemre Aug 11 '15 at 10:51
@TechJunkie Where can I find this "Clean all projects" menu? – Bikash Gyawali Oct 26 '16 at 08:47
clean build and build automatically both not working for me – Mahender Reddy Yasa Jun 01 '18 at 10:40
@BikashGyawali Project -> Clean... -> Check the checkbox "Clean all projects", click "Clean" – Kateryna S May 04 '23 at 18:13
I solved a local "import cannot be resolved" issue by renaming the file I was importing, and then naming it again to what it was originally. For example "TestService.java" -> "TestServiceNew.java" -> "TestService.java" – Kateryna S May 04 '23 at 18:16

score 19 · Answer 2 · answered Feb 17 '16 at 02:22

I've seen this happen and another approach to take which is similar to m0skit0 solution (if you are using Eclipse) is to right click on the project, select maven, select update project, make sure clean projects and refresh workspace are checked, and hit ok.

score 4 · Answer 3 · answered Oct 20 '15 at 12:11

4

After hours of struggle, creating a new Eclipse workspace, reimporting the projects and resetting up the same tomcat instance worked.

Probably the eclipse settings got messed up, and the deploy wasn't being done correctly anymore.

answered Oct 20 '15 at 12:11

Mihai Morcov

193
1
7

Actually, I had to delete the existing project and then import again the project – mmarquezvacas May 02 '18 at 22:19

The import cannot be resolved in eclipse

3 Answers3

Linked

Related