On Lun, 30 de Mayo de 2005, 22:00, Vadim Gritsenko dijo: > Jochen Kuhnle wrote: >> Hi, >> >> the EclipseJavaCompiler chokes on warnings, resulting in the XSP not >> working. This is because in line 365 (cocoon-2.1.8-dev), it checks >> against >> "result.hasProblems()" instead of "result.hasErrors()". I'd like to >> propose an option so the compiler ignores warnings and fails only if >> there >> are errors. However, there is more than one way to do this, so 'd like >> to >> ask before I create a patch: >> >> 1. Add a property "setIgnoreWarnings" to LanguageCompiler, configure the >> property in the "programming-language" section of cocoon.xconf and have >> CompiledProgrammingLanguage set it. >> >> 2. Avalonize the Compiler itself and make it configurable. >> >> 3. Other suggestions? > > Why not dump warnings into the log file (as WARNings), and stop only on > errors - > will this be possible?
Yep. This is posible, but maybe not desired. Best Regards, Antonio Gallardo.
