cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Piroumian" <kpiroum...@apache.org>
Subject Log level, compatibility (was: Re: DO NOT REPLY [Bug 20445] New: - i18n transformer does notrecognize 2.0 namespace)
Date Wed, 04 Jun 2003 06:14:04 GMT
From: "Bruno Dumon" <bruno@outerthought.org>
> On Tue, 2003-06-03 at 23:12, Joerg Heinicke wrote:
> > I guess, legacy support won't be readded, so this is a WONTFIX?
> >
>
> yes, I agree. A bit of a problem though is that upon encountering the
> old namespace, the I18nTransformer nicely logs a warning, however the
> log level is error by default. Maybe we should lower it to warn instead?

Btw, the WARNING text in 2.1 states:
>>>>
...
Until then, there will be no warranty that newer versions will maintain
backward
  compatibility for such parts, even in the most simple cases. Of course
  Cocoon will be compatible to latest release, 2.0.x release.
...
<<<<

Somewhat contradicting statements, arent they? Should the version 2.1 be
backward compatible with 2.0.x releases?

>
> (there are other components also logging deprecation warnings not
> visible by default)

+1 for lowering the log level to WARN.
But it'd be much better to provide two (or more) typical configurations,
e.g.:
  - development: log level - DEBUG, development cache settings, etc.
  - testing: log level - WARN, etc.
  - production: log level - ERROR, etc.

What do you think?

>
> -- 
> Bruno Dumon                             http://outerthought.org/
> Outerthought - Open Source, Java & XML Competence Support Center
> bruno@outerthought.org                          bruno@apache.org
>
>


Mime
View raw message