what worked for me (and probably not yet answered here till now) ::

while working on a selenium project and ant, i had copied and placed two different "build.xml" files from 2 different sources in the project's root directory. this resulted in this red-exclamation-mark, which disappeared as soon as i moved one of the build.xml file to another folder.

as to "why i had two build.xml files in one project?", i was actually playing around with ant's config from various build.xml files.


to remove red exclamation mark on project,
i have deleted all jar files using build path--> library --> add external jars and remove all or selected jar.
reinstall again.
this action resolve my issue with red exclamation mark.


if you are using maven pom.xml then check whether you have used dependency for poi-ooxml-schemas. i was getting the red exclamation as i was using version 3.17. changed the version to 4.1.2 and the red exclamation on maven disappeared. in other words what i meant to say was, use an updated version, this may help!!!


if it is maven project and your project view not having any issue. then try the following steps

right click the project ---> maven --> update maven


isn´t it a strange behavior? in my case, the mistake was that i added a jar-lib. but this lib was faulty, so i removed the lib. but, no matter what i´ve done, the error still exists. i removed the jar-file, even with the eclipse option "remove from build-path", deleted it on my project-folders and cleaned my project, but nothing worked. only after i´ve done the way qwert has described, it worked. but sould an ide not independent from error messages? the error was fixed, only the messages caused the problem. thanks to qwert (if i got enough reputations, i will vote your answer. but now i am not able to, sorry).


this is may for one reason, if a project contains library project then you need to clean first the library project have been used, then clean the project contains that library project.


i had a maven project giving me same thing. it showed that it couldnt find the jar with that version (dependency) and i knew its there and is correct -

so, for me the solution was to 1 delete the local repository. 2 clean the project. 3 disable the maven nature. 4 generate eclipse artifacts and 5 re-configure as maven project.

(in order)


my problem concerning exclamation mark was in the section: "right click on project folder" - properties - libraries tab. there was an error marked in red on a libray that probably wasn't in the right place so i removed it and ex. mark disappeared. the problem raised after deleting some old projects.


if your ide doesn't find jre from the path you given. then you manually need to add jre path in eclipse to remove red exclamation mark from the project. to do this please follow below steps :-

go to to properties>java build path>libraries> click on edit

then select alternate jre and click on finish.

note : if you don't have java run time environment (jre) installed, please install.


i was having the same problem....the actual issue was missing .jar file which took palce coz of changing my workspace. i just deleted the appcompat folder(which has the".jar" file) from my new workspace and copied it from my old workspace. this solved my problem.


mainly this problem occurs because your library files get deleted. the simple way to work your project as it was working previously is 1) go to project properties 2) select java build path 3) remove all library except jre. 4) now add the same same jar file by clicking "add external jars".


use this simple steps right click on the project->properties ->java build path-> click on the jre system library and remove it after that step click on add library and add a new jre system library that will resolve it!


for maven project delete the project from ide and run the maven command :-mvn eclipse:clean ,mvn eclipse:eclipse,mvn clean install -e .after this import the project on ide. this stuff is works for me.


if you are facing same issue :

  1. recall , if you have changed the place where you used to keep the jars and add it in build path .
  2. if you have moved your project from one machine to another then you need to right click on project-> build path -> configure build path . in tab order and export you would see the place where eclipse is searching for jars , just keep it there and refresh the project.
    1. if above things don't work , try project -> clean .


this is related to multiple versions of same depenendency in the local repository .m2

go to ur eclipse > problems tab > see the errors > go the local .m2 folder

delete all the non relevant versions of the the dependency which you have added recently.

then try to rebuild the project.


i too faced this strange situation. what i got to know is that, earlier i ran my spring projects with spring version 1.5.4 and later for one project i chose version 2.0.1. that's when i got this error. when i visited pom and changed spring version to 1.5.4 manually, the error was gone. what i guess is that, maven downloads the required jars according to the spring version specified. if you change the version, maven won't download jars if those jars are already downloaded for previous spring version and found in .m2 source folder found as c: -> users -> "logged-in-user-name" -> .m2 path.

what i did again was to keep the spring version as it is (as 2.0.1), i opened the problems view as said earlier and i deleted the jars which were said as not found in the problems view by visiting .m2 folder (the paths were mentioned in the problems view for were the jars are). i then updated the maven and all problems were gone.

that's how i conclude that the problem was with jars which were downloaded for the previous spring versions in .m2 folder.


if you change the location of the jars from selenium-java-3.13.0 folder this mak will appear. so restore the original location of the jars and you are go to go.


in my case this is incorrect/improper dependency

markers > problems is highlighting spring/.gradle/cache/httpcomponents.......pom is not valid archive

i removed

compile group: 'org.apache.httpcomponents', name: 'httpcomponents-client', version: '4.5.6', ext: 'pom'

changed to

compile group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.5.6'


i solved this problem by:

step 1: c:/user/rafiq/.m2/repository --> delete this folder

step 2: right click on your project-->maven-->update maven project-->check only clean project-->ok.

step 3: right click on your project-->maven-->update maven project-->check only update project-->ok.

problem solved.


it means the jar files are missing from the path that you have given while configuring build path/adding jars to the project.

just once again configure the jars.


mark circular dependcies as "warning" in eclipse tool to avoid "a cycle was detected in the build path" error. in eclipse got to :-> windows -> prefereneces -> java-> compiler -> buliding -> circular depencies



go to project -> right click -> properties -> java build path -> libraries

delete all the jars which have red cross symbol on the icon.



solutin 1:


right click on your project -> close project. it will close your project and all opened file(s) of the project


right click on your project -> open project. it will open your project and rebuild your project, hope fully it will fix red exclamation mark

solution 2:


right click on your project -> properties -> java build path. can you see missing in front of your library file(s) as per following screen-shot

step:2 click on add jar to select your jar file if it is the placed in web-inf/lib of your project or add external jar if jar file placed somewhere on your computer

step:3 select the old missing file(s) and click on remove click here for image

solutioin 3: right click on your project -> properties -> java build path -> jre system library and reconfigure the jre

and go to your project and remove .properties and .classpath in your project directories.

backup your project data and create a new one and follow the solutions 1 & 2


this is common, you will need to do the following steps:

1- right click on the project

2- build path

3- configure build path

4- remove jars/projects that had moved from their old path

5- clean the project

6- build the project "if not automatically built"

7- add the jars/projects using their new locations

run and that is it!


this is probably a build problem. what fixed mine was updating the project with maven (alt + f5)


there can be several reasons. most of the times it may be some of the below reasons ,

  1. you have deleted some of the .jar files from your /lib folder
  2. you have added new .jar files
  3. you have added new .jar files which may be conflict with others

so what to do is we have to resolve those missing / updating / newly_added jar files.

  1. right click on the project and go to properties
  2. select java build path
  3. go to the libraries tab
  4. remove the references of the jar files which you have removed already. there will be a red mark near them so you can identify them easily.
  5. add the references to the newly added .jar files by using add jars
  6. refresh the project

this will solve the problem if it's because one of the above reasons.


there might be some deleted jar files already in build path. right click on project. properties->java build path and removed deleted jar files from there.


i also had this problem several times and i could 'solve' it by just deleting the messages in the "problems"-tab and building the project again. select the project and click on the menu bar project -> clean... select your project again and okay.


it means there is a problem with the build path in your project. if it is an android project then it mostly means the target value specified in file cannot be found. this can also be caused because of other kinds of built problems. but it is shown mostly for built problems only. see here for more details. it is about built error decorater seen in eclipse.

an extract from that page:

build path problems are sometimes easy to miss among other problems in a project. the package explorer and project explorer views now show a new decorator on java projects and working sets that contain build path errors:

enter image description here

the concrete errors can be seen in the problems view, and if you open the view menu and select group by > java problem type, they all show up in the build path category:

enter image description here


there is a problems view (try window->show view) which shows this kind of thing.

it's usually missing jars (eg your project configuration references a jar that isn't there), and that kind of thing, in the case of jdt, but obviously these days eclipse can be used in so many ways, it could be anything.

Related Query

More Query from same tag