Community
Participate
Working Groups
In my company we use a Java Preprocessor to preprocess our sources before compiling. Right now it's integrated into Eclipse as an External Builder which runs a shell script which in turn applies the preprocessing stuff. In some scenarios the shell script can't do it's work and returns with an exit code which is not zero. That information however is desregarded by Eclipse. It would be nice if exit codes could be interpreted to cause a Build Failure for the project.
While exit codes like 0 are reasonably standard they are not universal. The external builder is not going to handle this for you. However it should be possible to provide some code to look at the result on do some additional processing. Perhaps one of the ant committers can elaborate.
To handle this properly, I think this would need to be configurable - i.e. allow the user to say which codes/ranges are fatal and which are acceptable. However, we don't currently have plans/resouces to do this. Contributions are welcome.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
