DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21386>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21386 Project.fireMessageLoggedEvent susceptable to incorrect state Summary: Project.fireMessageLoggedEvent susceptable to incorrect state Product: Ant Version: 1.5.3 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Project.fireMessageLoggedEvent sets the loggingMessage field to track whether BuildListeners are attempting to access System.err or System.out. The problem is that if any build listener throws an exception during message logging, the Project is left in an incorrect state. Any subsequent attempts to log a message results in the "... - infinite loop terminated" error message...even though no infinite loop is occurring. We are hitting this with Eclipse's Ant integration. One of the build listeners we use facilitate the user to cancelling a build. This build listener throws an "operation cancelled exception" which is handled etc. but we can do no further logging. I would propose that a try/finally block be introduced so that it is ensured that loggingMessage is set to false on exit of the method. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
