Berin Loritsch wrote:
Stephen McConnell wrote:
Hi Berin:
I was a little confused from the original [VOTE:DIFF] email. Basically the diff removed the avalon framework check but did not say anything about removing any files. Based on other feedback - it seems to me that it would be desirable to do something like the following:
logkit-compat-1.0.2.jar
logkit-2.0.jar
The logkit-compat-1.0.2.jar would contain all of the current depricated content and the logkit 2.0 would contain a clean release with all depricated classes and methods removed. This would provide a clean basis for moving forward with things like logging system conversion.
Thoughts?
I don't like it. Either we do LogKit 2.0 or we do LogKit 1.1.
LogKit 2.0 removes methods and classes.
LogKit 1.1 keeps everything the same.
Berin:
Seems to me that doing a LogKit 1.1 now brings LogKit up-to-date and can be done ASAP. With a LogKit 1.1 in place we can do a LogKit 2.0 that includes removal of deprecated content. Uses that are dependent on deprecated methods and classes can use LogKit 1.1. Others can move up to a clean 2.0. Personally I'm in favour of going to a clean 2.0 and skipping a 1.1 (but I'm not dependent on deprecated methods). If there are objections to this, then the 1.1 and 2.0 approach get as to same status of a clean LogKit release.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
