The project cannot be built until the build path errors are resolved.

Question

While compiling an android project in eclipse 3.4.2, I am getting The project cannot be built until the build path errors are resolved.

I got a temporary solution from the blog http://www.scottdstrader.com/blog/ether_archives/000921.html

The resolution was to force a resave of the selected projects (and their .classpath files):

Open the project properties
Select Java Build Path > Libraries
Add a new, arbitrary library (to be deleted later) > OK
Wait for the workspace to refresh (or force a refresh of the project)
The error(s) will go away
Remove the dummy library

The only other references I could find were to make minor alterations of contents of the .classpath file.

Is there any permanent fix for this issue?

What are the actual build path errors that you see? Also have you tried newer eclipse? 3.4 is somewhat outdated already. — Konstantin Burov, Sep 03 '10 at 02:49
It seems an issue with eclipse and happens in 3.5 as well on Mac. Whenever I want to build an android project I remove gen (automatically generated) folder and clean the project. — bhups, Sep 03 '10 at 03:47
Eclipse sometimes get stuck and won't ever get rid of an error. Try deleting it from the errors tab and re-building the project. Worked for me multiple times — Austyn Mahoney, Sep 03 '10 at 08:26
Helios Service Release 2, I just saw this after importing a project into the workspace. The "dummy library" solution was the only working solution I could find. — paiego, Jul 29 '11 at 04:46
+1 it helped me to continue to work, after one hour of cleaning temptatives.. the simple way of adding and successively remove a dummy library, worked. — morde, Jun 03 '13 at 21:56
This comment is almost three years after the original and I had the same problem with Eclipse Indigo after a power failure. In fact, the problem reoccurred three times after three power outages in a four hour period. Adding then removing a library entry worked every time. — user903724, Aug 08 '13 at 15:02
I did not add a library - at _Build Path > Order and Export_ I ticked the JRE lib - cleaned and voila! I then unticked the lib. See: http://utumno.github.io/blog/2014/05/02/eclipz/ — Mr_and_Mrs_D, May 03 '14 at 00:03
Go to project menu, enable the build automatically and click on clean — Lova Chittumuri, May 24 '17 at 08:28

score 144 · Accepted Answer · answered Sep 03 '10 at 18:06

144

Have you tried using Project > Clean... from the menu? This will force a new build on the selected projects in Eclipse.

answered Sep 03 '10 at 18:06

TK Gospodinov

8,302
6
24
25

i copied the installed sdk from the other system. its working fine now! – yokks Feb 02 '11 at 18:39
6

I had the same error. Eclipse had crashed and when I came back it said there was a build path error and wouldn't discuss what it was. No amount of cleaning or refreshing would fix it. This bogus "dummy library" was the only thing that worked! – JonLeah Jun 15 '11 at 16:19
5

No amount of Cleaning did it for me, tried removing/adding extra JARs as stated in other answers. Did not close Eclipse (ADT) by force, so the workspace was fine. Turns out **a simple Eclipse restart** did the trick. – cassi.lup Feb 28 '14 at 06:24
1

a simpler way, i have seen is to just do a minor change in the import order and eclipse will rebuild the build path and all errors should be resolved. – user2757415 May 06 '20 at 16:38
This still worked on Eclipse 2023-03, unbelievable! – le hien May 11 '23 at 03:40

score 66 · Answer 2 · answered Jun 26 '13 at 07:26

66

1-Right CLick on your project folder, Choose Build Path > Configure Build Path
2-Select Libraries Tab and delete any arbitrary library present there.
3-Click on Add Library option, Select JRE System Library and click Next.
4-Choose last Radiobutton option Workspace default JRE and click Finish.
5-press f5 for refresh.
6-run ur program .

answered Jun 26 '13 at 07:26

user2318214

661
5
4

1

haha, omg this caused even more problems and errors. Now I have missing artifact org.springframework:spring-context:jar:4.3.14.RELEASE – Zack Zilic Feb 18 '18 at 00:57

score 11 · Answer 3 · answered Jul 29 '16 at 01:06

This what fixed it for me...

I was having an issue with my spring-core.jar. I deleted the entire release directory located here. (I'm on win 10).

C:\Users********.m2\repository\org\springframework\spring-core\4.3.1.RELEASE

I right clicked on the project > Maven > Update project and my exclamation mark disappeared. No problems any more.

Here is the source where I found the information:

http://crunchify.com/cannot-be-read-or-is-not-a-valid-zip-file-how-to-fix-maven-build-path-error-with-corrupted-jar-file/

score 10 · Answer 4 · answered Apr 08 '13 at 23:50

This happens when libraries added to the project doesn't have the correct path.

Right click on your project (from package explorer)
Got build path -> configure build path
Select the libraries tab
Fix the path error (give the correct path) by editing jars or classes at fault

aimhaj · Answer 5 · 2022-02-25T08:26:30.100

8

This works for me: close the project then re-open it, this will force eclipse to reload a fresh project and detects the correct build path.

edited Feb 25 '22 at 08:26

answered Aug 19 '15 at 10:53

aimhaj

1,615
1
11
16

score 6 · Answer 6 · answered Jul 25 '16 at 14:01

None of the other answers worked for me. Even after fixing my build path issues, doing a refresh, clean, rebuild, and restart (of both eclipse and the computer), I was still getting the little red exclamation point.

I fixed it by closing the project (right-click, close project) and reopening it (double-click the closed project), which seemed to force eclipse to "notice" that the build path problems had been corrected.

score 4 · Answer 7 · answered Jun 14 '13 at 12:14

For my mac osx Eclipse, I followed following steps:

Right CLick on your project, Choose Build Path > Configure Build Path
Select Libraries Tab and delete any arbitrary library or anything else causing errors in Build Path.
Click on Add Library button, Select JRE System Library and click Next.
Choose last Radiobutton option Workspace default JRE and click Finish.
Clean and build your project.

score 4 · Answer 8 · answered Jul 02 '18 at 09:36

4

get a cmd and run

mvn eclipse:eclipse

answered Jul 02 '18 at 09:36

chamzz.dot

607
2
12
24

score 3 · Answer 9 · answered Mar 17 '18 at 13:58

3

This is what worked for me:

Go to ~/.m2/repository and deleted everything there by running rm -rf. Make sure everything is deleted.
Re-launch eclipse or STS
Right click on project -> Maven -> update project.

answered Mar 17 '18 at 13:58

Vikram3891

713
1
6
15

score 2 · Answer 10 · answered Jun 15 '14 at 03:31

2

On my Mac this is what worked for me

Project > Clean (errors and warnings will remain or increase after this)
Close Eclipse
Reopen Eclipse (errors show momentarily and then disappear, warnings remain)

You are good to go and can now run your project

answered Jun 15 '14 at 03:31

DamongoCoder

431
5
7

score 1 · Answer 11 · answered Jan 29 '13 at 20:53

I've seen this problem a few times (got it again right now on my home computer with Eclipse 4.2).

Forcing a resave (by changing the classpath e.g. by adding a library, save, change-back) works temporarily. But the problem comes back when Eclipse is restarted :(

Nuking the Eclipse workspace from orbit will permanently fix it (until next time). But there must be a better way!

score 0 · Answer 12 · answered Jan 07 '14 at 16:36

0

just check if any unnecessary Jars are added in your library or not. if yes, then simply remove that jars from your library and clean your project once. Its worked for me.

answered Jan 07 '14 at 16:36

user3133845

23
1
1
4

score 0 · Answer 13 · answered Feb 26 '14 at 11:34

0

In Eclipse this worked for me: right click project. -> Properties -> Library Section; Add (any library at all) -> select library and click remove -> press okay.

answered Feb 26 '14 at 11:34

jimbob

3,288
11
45
70

score 0 · Answer 14 · answered Jan 24 '18 at 04:28

I ran into this annoying issue with the Play framework. It would be nice if there was some way of knowing what build errors Eclipse is unhappy about, but it's not going to tell you. With one project, I was able to close the project, rebuild the Eclipse configuration with sbt eclipse, and reopen. With an almost identical project, that didn't work. But deleting the project, rebuilding the Eclipse configuration with sbt eclipse, and importing, did the trick.

score 0 · Answer 15 · answered Jun 27 '19 at 07:21

0

If you think you've done everything correctly but Eclipse still complains about the jars, refresh the folder where the jars are and make sure eclipse knows they've been added to the project. Specifying the file path alone is (apparently) not enough

answered Jun 27 '19 at 07:21

DGK

2,947
5
32
47

score 0 · Answer 16 · answered Nov 19 '19 at 06:33

I've faced this issue a couple of times and following the below steps has resolved both the times. 1. Navigate to C:\Users\ 2. locate the ".m2" folder and delete it.

Now navigate to the particular project in eclipse and Right-click on the project > Maven > Update Project

wait until the project is updated and in my case following the above steps resolved both the times.

score 0 · Answer 17 · answered May 31 '20 at 14:35

I was getting an additional warning

The compiler compliance specified is 1.6 but a JRE 1.8 is used

Resolving this warning make the error also go away. The steps are as follows:

I right-clicked on it, then clicked on Quick Fix. From the dialog that opened I selected Open the Compiler Compliance property page, and clicked the Finish button.

(This is same as Java Compiler section.)

In this dialog I found the Compiler compliance level drop down and changed 1.6 to 1.8, and clicked on Apply and close.

I got a message box Compiler Settings Changed which asked if I wanted to Build the project now?. I clicked on Yes.

The build path error went away.

score 0 · Answer 18 · answered Sep 15 '20 at 06:55

0

Go to > Right CLick on your project folder > Build Path > Configure Build Path > Libraries Tab > remove project and external dependencies > apply & close

Now, Gradle refresh your project.

answered Sep 15 '20 at 06:55

saurabh gupta

491
6
18

score 0 · Answer 19 · answered Nov 29 '20 at 04:19

0

Added below to pom.xml file and it worked eventually: 

<dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>javax.servlet-api</artifactId>
    <version>4.0.0</version>
    <scope>provided</scope>
</dependency>

answered Nov 29 '20 at 04:19

appdesigns

114
1
11

score -1 · Answer 20 · answered Sep 12 '14 at 16:50

-1

Goto to Project=>Build Automatically . Make sure it is ticked

answered Sep 12 '14 at 16:50

HimalayanCoder

9,630
6
59
60

The project cannot be built until the build path errors are resolved.

20 Answers20

Linked

Related