cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35162] - [PATCH] EclipseJavaCompiler chokes on warnings
Date Mon, 19 Sep 2005 21:07:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35162>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35162


joerg.heinicke@gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From joerg.heinicke@gmx.de  2005-09-19 23:07 -------
AFAIK (from my experience with JCI) errors are a subset of problems and that's
exactly what is needed here. In JCI all problems are handled, but the actual
problem is asked for isError() to know whether it is a warning or an error.
Cocoon's Compiler interface has only getErrors(), so it's valid to change it to
hasErrors() and getErrors().

BTW, I still plan to write a JCI based implementation of Cocoon's compiler
interface meaning every compiler supported by JCI will be automatically
available in Cocoon.

Fixed in both branch and trunk.

Thanks for bug report and patch. Please cross-check and close the bug.

Jörg

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

Mime
View raw message