avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9444] - Back Compatibility Fix for AbstractLogEnabled
Date Tue, 28 May 2002 08:17:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9444>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9444

Back Compatibility Fix for AbstractLogEnabled





------- Additional Comments From jeremias.maerki@outline.ch  2002-05-28 08:17 -------
Worksforme means: I've had the same problem and had to find a work-around until 
FOP was changed to use LogEnabled. For me it meant leaving some of my Avalon-
based components on AbstractLoggable.

The simple truth is: changing from Loggable to LogEnabled is not backwards 
compatible. You've got to watch dependencies. Loggable has a dependency on 
LogKit, as has FOP 0.20.3. LogEnabled does not, so there's the problem. You 
can't always expect a component to still work when you update the thing that it 
depends on. Sometimes it means you're stuck with some older stuff until all 
dependant components are updated.

Have a look at all the discussion about Loggable and LogEnabled for ECM. It's 
not so simple to provide backwards compatibility in this case.

--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message