cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Kuhnle <>
Subject XSP: EclipseJavaCompiler chokes on warings
Date Fri, 27 May 2005 18:16:04 GMT

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?

Note that this is important, because some warnings cannot be circumvented, 
e.g. JDK 1.5 type safety warnings when using legacy code.


View raw message