score:185

Accepted answer

according to the documentation:

decorates java projects and working sets that contain build path errors

in practice, i've found that a "build path error" may be caused by any number of reasons, depending on what plugins are active. check the "problems" view for more information.

score:0

the solution that worked for me is the following one given..

i selected the particular project> right click >build path>configure build path> libraries> i noticed that jre system library was showing(unbound) hence..

selected that library>click on remove>click on apply>click on add library>jre system library>next>workspace default jre>click on finish>apply>ok.

now you will not see these exclamation icon in your project.

score:1

also be sure you dont have any closed project in the projects tab ->

https://i.stack.imgur.com/stgeu.png

score:2

make sure you don't have any undefined classpath variables (like m2_repo).

score:2

i had the same problem and andrew is correct. check your classpath variable "m2_repo". it probably points to an invalid location of your local maven repo.

in my case i was using mvn eclipse:eclipse on the command line and this plugin was setting the m2_repo classpath variable. eclipse couldn't find my maven settings.xml in my home directory and as a result was incorrectly the m2_repo classpath variable. my solution was to restart eclipse and it picked up my settings.xml and removed the red exclamation on my projects.

i got some more information from this guy: http://www.mkyong.com/maven/how-to-configure-m2_repo-variable-in-eclipse-ide/

score:2

the solution that worked for me is the following one given by steve hansen smythe. i am just pasting it here. thanks steve.

"i found another scenario in which the red exclamation mark might appear. i copied a directory from one project to another. this directory included a hidden .svn directory (the original project had been committed to version control). when i checked my new project into svn, the copied directory still contained the old svn information, incorrectly identifying itself as an element in its original project.

i discovered the problem by looking at the properties for the directory, selecting svn info, and reviewing the resource url. i fixed the problem by deleting the hidden .svn directory for my copied directory and refreshing my project. the red exclamation mark disappeared, and i was able to check in the directory and its contents correctly."

score:4

what i did was peculiar but somehow it fixed the problem. pick any project and perform a fake edit of the build.properties file (e.g., add and remove a space and then save the file). clean and rebuild the projects in your workspace.

hope this solve some of your problems.

score:6

i found another scenario in which the red exclamation mark might appear. i copied a directory from one project to another. this directory included a hidden .svn directory (the original project had been committed to version control). when i checked my new project into svn, the copied directory still contained the old svn information, incorrectly identifying itself as an element in its original project.

i discovered the problem by looking at the properties for the directory, selecting svn info, and reviewing the resource url. i fixed the problem by deleting the hidden .svn directory for my copied directory and refreshing my project. the red exclamation mark disappeared, and i was able to check in the directory and its contents correctly.

score:9

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 jar file references 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.

score:16

i also faced a similar problem when i tried to import source file and jar file from one machine to another machine. the path of the jar was different on new machine compared to old machine. i resolved it as belows

  1. right click on the "project name"
  2. select "build path"
  3. then select "configure build path"
  4. click on "libraries"
  5. remove all the libraries which were referring to old path

then, the exclamation symbol on the "project name" was removed.

score:17

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 project.properties 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


Related Query

More Query from same tag