Community
Participate
Working Groups
Build Identifier: 20110615-0604 If there is a build path error there is the above error message in the problems view and an exclamation mark on the project. This is very easy to overlook, especially if you compile with eclipse and deploy your artifacts with ant to an app server, so you actually deploy old code. There should be a stronger warning for this situation, e.g. make the problem view come to front and place the selection onto the error line. Reproducible: Always
Umm...i guess one doesn't deploy as regularly as one makes changes to the code. Atleast once before deploying its always a good idea to check the problems view (even if there is no error, there might be extra compiler warnings). Even if that's not a practice you follow, the exclamation mark is easily spotted. Markus, what is your opinion on this?
Problem is, the red exclamation mark is there quite on projects, and quite often harmless, e.g. a compiler error in a currently non-used test class can be ignored for the moment. But "cannot be built" is fatal and should be treated differently, else you wonder why running your main class yields the same results as last time ;-)
The red exclamation mark is usually *not* harmless, since it only shows up if you have build path errors. For other errors, you get a normal error badge. To always see whether you have build errors in your workspace, you can e.g. configure a Problems view to only show Java Build Path Problems and then turn this view into a fast view (the icon will still update).
