The import cannot be resolved eclipse ошибка

I’m trying to work with Hibernate in Eclipse.
I’m creating a new simple project and I’ve downloaded a collegue project too, via CVS.
Both don’t work, while on my collegue’s Eclipse do.
The problem is that, for each import of an Hibernate class, Eclipse says:

The import org.hibernate cannot be resolved

But all Hibernate jars are in the build path, that is:

antlr-2.7.6.jar
cglib-2.2.jar
commons-collections-3.1.jar
dom4j-1.6.1.jar
hibernate3.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
javassist-3.12.0.GA.jar
jta-1.1.jar
slf4j-api-1.6.1.jar

asked Dec 1, 2010 at 9:30

bluishbluish

25.6k27 gold badges119 silver badges177 bronze badges

Try cleaning your project by going to the following menu item:

Project > Clean...

If that doesn’t work, try removing the jars from the build path and adding them again.

answered Dec 1, 2010 at 9:39

dogbanedogbane

262k75 gold badges391 silver badges411 bronze badges

Obviously there are cases where there is a valid issue however Eclipse throws this error for no good reason sometimes. This is still (in v 2020-09) an old (2010) Eclipse bug that can be resolved by making a negligible change to the project settings.

touch .classpath

solves the issue, or go to Project > Properties > Java Build Path > Order and Export > make a meaningless order change > Apply. Changing the order back does not regress to the problem.

answered Jul 15, 2016 at 20:55

user1133275user1133275

2,58727 silver badges30 bronze badges

If is a Maven project, also click on Maven >> Update project… (F5)

Update Maven project

answered Dec 14, 2016 at 7:56

albertoiNETalbertoiNET

1,20024 silver badges32 bronze badges

Clean the project. And double-check the jars being really on the build path (with no errors). Also make sure there is nothing in the «Problems» view.

answered Dec 1, 2010 at 9:38

BozhoBozho

582k141 gold badges1052 silver badges1136 bronze badges

I found the problem. It was the hibernate3.jar. I don’t know why it was not well extracted from the .zip, maybe corrupt. A good way to check if jars are corrupt or not is navigating through their tree structure in «Project Explorer» in Eclipse: if you can’t expand a jar node probably it’s corrupt. I’ve seen that having corrupt packages it’s frequent when you drag and drop them to the «Project Explorer». Maybe it’s better to move and copy them in the OS environment! Thankyou all.

answered Dec 1, 2010 at 10:26

bluishbluish

25.6k27 gold badges119 silver badges177 bronze badges

I solved it by removing the project (do not delete on the disk) and importing it again.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered May 28, 2015 at 7:46

clean project
Project — > clean…
Right click on project — >BuildPath — >Configure BuildPath — >Libraries tab — >

Double click on JRE SYSTEM LIBRARY — >Then select alternate JRE

answered Jan 22, 2018 at 12:18

This has solved my issue.

1) clean project Project -> clean…

2) Right click on project -> BuildPath -> Configure BuildPath -> Libraries tab ->
Double click on JRE SYSTEM LIBRARY -> Then select alternate JRE

3) Click Save

4) Again go to your project in project explorer and right click to project -> BuildPath -> Configure BuildPath -> Libraries tab ->
Double click on JRE SYSTEM LIBRARY -> This time select «Execution Environment»

5) Apply

Nisarg

1,6336 gold badges18 silver badges31 bronze badges

answered Aug 23, 2018 at 19:04

I had the problem, that the classpath was broken somehow.

So right click on the project in Package explorer > Plug-in tools > Update classpath… did it for me

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Jun 22, 2012 at 7:51

wuppiwuppi

1,00410 silver badges16 bronze badges

I resolved this issue by updating the project: right click on the Maven project, select Maven -> Update Project -> select checkbox Force Updates of Snapshots/Releases.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Jul 26, 2019 at 8:41

Try adding JRE System Library in the build path of your project.

answered Jun 19, 2013 at 7:39

Gaurav PantGaurav Pant

3331 gold badge3 silver badges5 bronze badges

With me it helped changing the compiler compliance level.
For unknown reasons it was set to 1.6 and I changed it to 1.8.

Once at project level right click on project > Properties > Java Compiler, while in Eclipse click on menu Window > Preferences > Java > Compiler.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Aug 1, 2017 at 12:46

Alex P.Alex P.

3,0013 gold badges21 silver badges32 bronze badges

I tried all of the answers above but no luck. In my case, there is a generated build/classes folder with some additional «.class» files. I ended up going to the package explorer, right-clicking on the project and selecting the «Refresh» option and that made the build/classes folder available again resolving the issue.

answered Feb 21, 2018 at 19:28

egallardoegallardo

1,2341 gold badge15 silver badges25 bronze badges

In my case it was a broken jar in the Maven repository. Delete jar files in repository and let Maven download them again.

When I ran mvn clean install from the command line, it ran fine, but Eclipse still could not compile the code. When I ran maven install in Eclipse then I saw that Maven complained about bad jar file. So I deleted it and ran maven install again. The problem was gone.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Aug 24, 2018 at 9:28

In order to download non-existing jar file in your .m2 directory, you should run mvn clean install command for your project pom.xml. Then you should update the project dependencies by clicking Alt+F5. This works for me!

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Jan 15, 2019 at 10:46

ÖMER TAŞCIÖMER TAŞCI

5185 silver badges9 bronze badges

Removing the «module-info.java» did resolve the issue for me!

This file was automatically generated and did appear in my hierarchy…

answered Apr 4, 2019 at 15:46

val_tval_t

211 bronze badge

I had the same problem because I added a jar I created, where I had set the packaging base directory other than the base directory of the classes.
As a result the class e.g. java.util.List had to be imported as util.List although the suggested import was the first one.

Check the imported jars under referenced libraries to see that they are imported correctly

answered Oct 25, 2012 at 10:04

kon psychkon psych

6161 gold badge11 silver badges26 bronze badges

I didn’t understand the reasoning behind this but this solved the same problem I was facing. You may require these steps before executing steps mentioned in above solutions (Clean all projects and Build automatically).

right click project -> Properties -> Project Facets -> select Java -> Apply

answered Jul 8, 2016 at 16:26

avpavp

2,71228 silver badges33 bronze badges

Whenever you come across this problem just go to Project > Clean, then select Clean all projects. It should get resolved, otherwise try to delete those jars and add them again. Last thing would be to try restarting Eclipse.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Dec 28, 2016 at 18:33

pom.xml

If it’s a Maven project, go to pom.xml and remove all the dependency jars. Save it. Project will automatically build.

Then add dependency jars again (you can do Ctrl+Z). Save it. Project will automatically build and you won’t see that error.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Aug 28, 2019 at 6:39

sravansravan

1311 gold badge1 silver badge7 bronze badges

Solution for Eclipse IDE

In my case I fixed it by correcting one of these two files that may be corrupt: .classpath or .project.

To repair any of the corrupted files, you can copy from another project that has both the .project file or .classpath file in question and is error-free. But be sure not to add additional settings that will not be used.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Nov 25, 2019 at 14:08

Remove the dependency in your POM.XML and download the jar and add it in buildpath.

sometime -> maven will not reflect new changes and this might cause this kind of prob

answered Jan 30, 2020 at 13:50

right-click src->new package: Rename the package that you want to import and create a new class with the package class name.
E.g if import net.proteanit.sql.DbUtils; show import error

then create a new package with the name net.proteanit.sql
and make class DbUtils;

package net.proteanit.sql;
public class DbUtils {

}

Suraj Rao

29.3k11 gold badges96 silver badges103 bronze badges

answered Dec 5, 2021 at 4:09

Please try and check whether all the libs are in place. I had the same issue. But I solved it by moving the lib folder and adding all the jars again in the build path.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Mar 11, 2014 at 9:35

I got the same problem. I downloaded the jar and added it to the build path, but I didn’t notice that the extension was .jar.zip. I again converted it to .jar and added to the build path.

It solved my problem. It’s a very silly mistake but I wrote it here in case it could help someone.

bluish

25.6k27 gold badges119 silver badges177 bronze badges

answered Sep 18, 2014 at 5:12

smalismali

4,6076 gold badges36 silver badges58 bronze badges

If you are working with Maven and have this problem, check the repository server (for example nexus server), if the artifact is there. Sometimes, they can change the name of the artifact and you try to get the artifact with its old name.

answered May 10, 2016 at 10:15

drJavadrJava

6872 gold badges9 silver badges24 bronze badges

Resolved by linking the source. From the explorer right click on the project, select properties, select Java Build Path, select Source from tabs, press button «LinkSource». And specifying the folder to add to the project.

answered Jul 19, 2017 at 14:47

I couldn’t import as well.
Took me some hours to figure out, that I tried to use a 1.6 bound library/jar, while I was trying to compile for 1.8.
When I switched my project also to use 1.6, the import issue has gone.
All error messages were leading into wrong directions.
Just in the source I found some limitations directing to 1.6 version.
And:
For example the .settings and .classpath (File-Search) -> org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6
can give a hint, on such issues.

answered Oct 27, 2018 at 12:13

I faced the same issue and I solved it by removing a jar which was added twice in two different dependencies on my pom.xml. Removing one of the dependency solved the issue.

answered Dec 20, 2018 at 18:20

ReemaReema

5873 gold badges12 silver badges36 bronze badges

Источник

When you start to develop web application using Java, you may think to use Eclipse as the IDE. Assume that you have seen a good tutorial about Java servlet on the internet or read the chapter of a book discussing about web development using JSP.

You are now writing the first servlet by using the wizard provided by the IDE. However, as soon the template file is loaded on the source code editor, you encounter the infamous error “The import javax.servlet cannot be resolved” just like depicted in the figure below.

Servlet import error

This error is normal. Servlet library is not shipped by default in Eclipse. You also can’t find the library in JRE/JDK package you download. Instead, you will find it in the lib folder under Tomcat installation directory like depicted below.

Servlet API jar file

So, how can we resolve the error? The solution is apparently simple. We just need to add the servlet jar file into the build path. Based on the scope, we can achieve this using two methods; single project-wise and all projects-wise. Both methods will be explained immediately. You just need to pay attention that these methods were tested under the following system environment and steps in other environment may vary:

OS: Windows
Eclipse version: Eclipse 3.5 Ganymede
JDK version: JDK 1.6.0_14

In the first method, we add the servlet-api jar by right-clicking the project name and choose Properties option. After clicking, a new popup window will appear. Click the “Java Build Path” menu on the left followed by choosing “Libraries” tab. Subsequently, click “Add External JARs” button and point to servlet-api.jar in lib folder of Apache Tomcat installation directory. If you do all these steps correctly, you will notice that servlet-api.jar has been added into the libraries. Please check your result with the reference picture below.

Adding servlet API into project library

Click “OK” to complete the modification. After a glance, you will notice all imports errors have been disappeared.

The first method is good if you rarely work with servlet. If you yourself are a very busy developer who has to build numerous projects for your vast client base, it is considerably wise to apply the second method. In this method, we will add the servlet-api.jar into the JDK directory. After the modification, you will never encounter the error again as the servlet-api.jar will always be in the build path. This is different with the previous method which requires you to modify the project properties again if you create a new dynamic web project.

To execute the second method, follow the instructions below:
1. In Eclipse workbench, choose Window > Preferences
2. Choose Java > Installed JREs on the left menu
3. Focus on the JDK you want to modify, click “Edit”. A new popup will appear

Adding servlet API JAR file into universal build path

4. Click “Add External JARs” and point to servlet-api.jar in lib folder of Tomcat installation directory.

Adding Servlet API JAR file into universal build path-2

5. Click “Finish” to close the second popup and “OK” to complete the modification

After you do all the steps, all the servlet import errors in the source code editor will have vanished. You will also have discarded the import error for all projects which require the servlet functionalities.

Источник

⛔️ The import javax.servlet can’t be resolved

import java.servlet cannot be resolved error.png

If you receive the above error message in your java files (servlet classes) while working with eclipse IDE then you are most probably missing the API servlet-api.jar file that is needed by your project.

How to resolve javax.servlet error!

Make sure that you have installed Apache Tomcat Server and have configured it to run your Application.
Right Click on your Project folder,
Now click on Properties at the bottom

Right-Click-on-Project-Folder-and-Select-Properties.png

Select Java Build Path on the right.
Go to Library tab.
Click on Add External Library.
Now go to the location where Apache Tomcat has been installed (e.g. : c:apache-tomcat-7.0.101).
Now go to lib directory and Select servlet-api jar file.
Apply Changes (Save).
Just Clean + Build your project.
The errors must now get resolved.

Add-servlet-api-jar.png

Note: Alternatively, you just copy the servlet-api jar file to the lib folder of your project

package com.code2care.org;


import javax.servlet.*;
import javax.servlet.http.*;
import java.io.PrintWriter;
import java.io.IOException;

public class ServletError extends HttpServlet
{


  /**
   * HTTP doGet request.
   */
  public void doGet(HttpServletRequest request, HttpServletResponse response) 
  throws ServletException, IOException
  {
   
    response.setContentType("text/html");
    PrintWriter out = response.getWriter();
    out.println("");
    out.println("Resolving Servlet Jar exception");
    out.println("");
    out.println("Get : This works!.");
    out.println("");
    out.close();
  }

  /**
   * HTTP doPost request.
   */
  public void doPost(HttpServletRequest request, HttpServletResponse response) 
  throws ServletException, IOException
  {
  

    response.setContentType("text/html");
    PrintWriter out = response.getWriter();
    out.println("");
    out.println("Resolving Servlet Jar Exception");
    out.println("");
    out.println("Post : This works!.");
    out.println("");
    out.close();
  }
}

Источник

The import org.hibernate cannot be resolved

But all Hibernate jars are in the build path, that is:

antlr-2.7.6.jar
cglib-2.2.jar
commons-collections-3.1.jar
dom4j-1.6.1.jar
hibernate3.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
javassist-3.12.0.GA.jar
jta-1.1.jar
slf4j-api-1.6.1.jar

30 Answers

Try cleaning your project by going to the following menu item:

Project > Clean...

If that doesn’t work, try removing the jars from the build path and adding them again.

touch .classpath

solves the issue, or go to Project > Properties > Java Build Path > Order and Export > make a meaningless order change > Apply. Changing the order back does not regress to the problem.

Clean the project. And double-check the jars being really on the build path (with no errors). Also make sure there is nothing in the «Problems» view.

If is a Maven project, also click on Maven >> Update project… (F5)

Update Maven project

I solved it by removing the project (do not delete on the disk) and importing it again.

clean project
Project — > clean…
Right click on project — >BuildPath — >Configure BuildPath — >Libraries tab — >