My mistake -
Logging is a hot issue for me right now. The current logging
that's used in the James version we are running is rather
worthless to an ISP administrator - even to a Java
developer, these multiple log files are not very informative
nor consistant.
When the logging issue came up here in the list, I jumped in
as I wanted to be instrumental in both it's conceptual birth
as well as design and deployemnt.
The response I received was that , "Yes, it's needed but not
now." so I backed off.
With this patch - which is really you adding some tracking
to an area you are monitoring - I got all huffy and thought,
"Hey, what is this; we shouldn't be developing down this
dead end.."
Has the code been frozen yet or are you still making these
mionor changes ?
Has the release date been set so one can start thinking
about the branch - or has that not been decided yet ?
and finially, who are the primary 'Committers' and which of
them are PMC's for James ??
Thank you,
Alan Gerhard
> We talked about making changes to mailet logging after the
> release. I don't recall anything about not changing
> logging within James, which uses Avalon Logging Framework.
> Everyone seems relatively accepting of that logging
> mechanism within James, itself.
> --- Noel
--------------------------------------
This EMail Was brought to you by
WebMail
A Netwin Web Based EMail Client
http://netwinsite.com/webmail/tag.htm
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
