Berin Loritsch wrote:
LogKit is at the bottom of our food chain, and there are some minor
issues we need to work out before we do a release. Below is the
order of precedence. If we cannot get consensus we will take the
easiest route to get a release.
#1 Remove circular dependency on Framework
-------------------------------------------
The particular class that forces the dependency is an "Avalon"
formatter that can handle the nested exceptions from Avalon.
It is a hold-over from when we did a first release after we
moved to Jakarta. I think it is relatively safe to remove the
class as it merely extends the correct version. It has been
deprecated from about the second release.
+1 from me.
me too +1
#2 Maven integration for build ------------------------------- The build is very simple, and nothing really major needs to be done. LogKit's Ant build isn't problematic, so it is ok to leave it alone as well. The question is before or after release? If we cannot resolve the issue soon, we will merely make it after the release.
Putting in place a Maven build in parrallel with the ant build is not going to harm anyone. In fact its a positive thing because it lets us experiment a bit. With the resolution of the recusvie depedency stuff noted above - this becomes easy and provides a good starting point for people who want to experiment. I.e. Maven is this context is not a release issue - it just a good idea. We the realease against ant and publish against the result of the ant build.
#3 Documentation ----------------- LogKit documentation is fairly sparse. We have *something*, but nothing that covers all the features and how to set it up. The current docs are OK while we make a quick release, but we do need to put some attention into those docs soon. LogKit hasn't changed much, so there is a good chance the docs will be good for a long time. We could release now, and add docs as they come in to the web site.
I'm not too fussed about this - the only complains I've been receiving about logkit concern the absence of the ability to release a logging channel. I havn't seen any issues concerning documentation (which is not the same case for Excalibur logger - but that's further down the food chain).
Aside from a few Status changes, and the resolution of these issues, there should be nothing holding back the release of LogKit.
I agree. 1. lets eliminate the recursice dependency. 2. get a good clean framework independent build in place 3. release Next stop - framework. Cheers, Steve.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
