> -----Original Message----- > From: Curt Arnold [mailto:[EMAIL PROTECTED] > Sent: 25 May 2005 23:59 > To: Log4J Developers List > Subject: Re: Remove TRACE? Was: [VOTE] Modified Release Proposal > <snip/> > > What we need to make sure is that we have a reasonable incremental > migration path from where we are to where we want to go. For example: > > log4j 1.2.11 and earlier: > > Level is non-final, constructor is protected. Custom levels require > extending Level or bypassing constructor access modifier. Category > exists. No mechanism for configuring custom thresholds. > > log4j 1.2.12 (alternatively 1.3): > > Level is non-final with new public constructor. Category exists. > Configuration should be modified to take at least an integer as an > alternative and possibly registration of new levels with > configurators. Existing protected constructor marked as deprecated. > > log4j 1.3 or 2.0: > Category removed. Level is final. > > > Somewhere along there we might deprecate Level.toLevel() et al.
I don't see how you could make Level final in a 1.x release. As you can not deprecate the class, how will you let users know that their custom levels will no longer work? > I'd like to avoid a global registry of Level's since different parts of > an application might have assigned different severities to their > "ULTRATRACE". Having configurations can accept integer severity > values (which is all that is needed to evaluate the thresholds) would > allow an app to be configured without needing to be aware of all the > levels used within its dependencies. > > If we depend on integer severities to configure thresholds to custom > levels, then it may be good to provide a %severity format specifier > so you could actually see the integer values in log so you know how > to tweak them. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
