Klaus.Bartz at coi.de
Wed Nov 29 10:12:43 CET 2006
I think all developer of IzPack knows that there are some
points in the product which are not optimal solved. Of course,
we should solve it if possible and time is right on work-time-device.
Some weeks ago I have had a little problem with logging; I log
some things which are interested especially for me, but it will be
logged if logging is activated. One user persisted on the
meaning that the logged information was fatal for IzPack.
Therefore it will be nice if the new logging stuff will be support
different topics (as you have decribed) and logs a prefix. May be
configurable what topic should be logged.
>From: izpack-devel-bounces at lists.berlios.de
>[mailto:izpack-devel-bounces at lists.berlios.de]On Behalf Of Elmar Grom
>Sent: Wednesday, November 29, 2006 12:44 AM
>To: izpack-devel at lists.berlios.de
>Subject: [izpack-devel] Logging
>Just a quick answer on the remarks by Markus Schlegel,
>"After working for some days with izpack, I have to mention,
>gulping a general Exception is not a good practice. You should
>some logging api to log such exceptions - just for
>troubleshooting. It's ok
>for specific exceptions that are expected to be thrown. So if
>you plan to
>make some refactoring in the future, this may be a point to look at."
>Markus is absolutely right. I think there is some work left in
>ensure it really is as stable as we all would like and that
>encountered during installation are reported to the operator.
>A couple of days ago I sent out a message with the following
>"Proposal for Messenger class"
>This is a proposal about a logging infrastructure to deal with
>issue. In the meanwhile it is mostly implemented and ready to
>with IzPack. In the near future there will be some messages to
>input and support on a number of related topics. Logging calls
>will be very
>simple to implement, so I hope there will be heavy use of this
More information about the izpack-devel