- This topic has 1 reply, 2 voices, and was last updated 16 years, 4 months ago by
.
-
Posts
-
When I do a build it finishes and I get the message Build Successful, but there are errors in at least one of my Java files. MyEclipse Blue 6.5.1 is putting a red X on the errors. One of the errors is The method trim() is undefined for the type Integer . I would like the Build to fail when I have an error like this. Is there a setting somewhere that tells MyEclipse to Ignore errors ? I have looked but can’t find it ? Anybody know where it is ? Thanks
The build will die of natural causes if you have too many errors, or fundamental errors like a busted build path, but you cannot set the build to stop simply on a single compilation error like that, the reason is because the build process *itself* is what is used to determine where errors are.
Also, sometimes 1 error can cause 10 spurious/secondary errors and the real fix is just to fix that 1 error, stopping as soon as *1* error pops up could possibly put you in a position where you wouldn’t be able to fine the core/root error that needed to be fixed and could only see the secondary side-effect errors from it.
That’s why the build always tries to run to completion, to give you a complete picture of “what is wrong”.
