When you right-click the Eclipse Proj build path==>organize build Path , in the pop-up window, find the Libraries tab, and you can get that some jar sets are red forks.Jar package does not discover the equivalent file , producing a red exclamation mark(!) in opposite of the Eclipse project, maybe due to an outsided introduced item or due to some files were erased, causing in a red exclamation point. Find the jar packages that are not in these eclipse projects, remove them, and then re-import the compulsory jars manually.
Red exclamation shows that somewhat goes incorrect with occupied copy
working.
Case 1 & Solution
Maximum common situation is using outsided build process which make some hurt to occupied copy. For instance it can duplicate svn folders from source folders into equivalent binaries folders. In that situation derivative .svn folders is located in incorrect path. So, mistaken working copy portions are striking with red exclamation.
To escape this state you can precise your build procedure in stop repetition of .svn folders. Alternative way is do not use external builders.
Top comments (0)