james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: [PATCH] SMTPHandler logging
Date Sat, 05 Oct 2002 16:14:21 GMT
Alan,

By all means, if you have issues with James, logging or otherwise, please
contribute.  The request from Danny was specifically related to mailet
logging, which may require changes to how mailets do logging.  He'd like to
defer that discussion until after this release has been put out.  James,
itself, uses Avalon Logging.  That not been proposed to change.  By all
means, if you have a list of logging issues, please write them up.  Just
please separate mailet logging issues from James logging issues.

If you want all of the logging to go to a single file, edit the log targets
in james-server.xml (aka environment.xml).

With respect to the release schedule, Danny indicates that the propose
release schedule should be considered as adopted.  Peter indicates that he
still has a section of code to check in.  I'm not planning anything not
related to a bug fix.  In this case, I've seen some anomalous behavior that
I'm trying to isolate, plus it seems to me a generally useful log entry.  Do
you have an issue with the content of the log entry?

The Committers are listed at: http://jakarta.apache.org/james/weare.html.

	--- Noel

-----Original Message-----
From: alan.gerhard@mail.gercom.com [mailto:alan.gerhard@mail.gercom.com]
Sent: Saturday, October 05, 2002 0:48
To: James Developers List
Subject: RE: [PATCH] SMTPHandler logging


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
minor 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


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


Mime
View raw message