I haven't much time for this today, but here's my initial thoughts:
- As it is, my last bought of logging upgrades made the default
lookup order: LogKit, Log4j, JDK logging, and StandardOutLogChute
(which sends error to Std.out and error to Std.err). This still
seems appropriate for me and
So - if a user deploys this without the Avalong LogKit there's no
velocity.log automatically created?
That seems ok to me.
WILL
On 10/10/06, Nathan Bubna [EMAIL PROTECTED] wrote:
I haven't much time for this today, but here's my initial thoughts:
- As it is, my last bought of logging
Quick followup on this, then. Maybe we should leave the Avalon Log
Kit out of the velocity dependency jar?
My objective is to make this simpler for casual or new users. I'd
think at this point the Avalon approach doesn't add a lot of value for
that crowd. Those who want it can copy it into
Yes, if neither LogKit (which is in velocity-dep, IIRC) nor Log4j are
available to Velocity, then there is no velocity.log automatically
created.
Formerly, if neither were available, Velocity would panic and quit.
Now it will fall back to first looking for JDK logging, and if it
can't find that,
+1
On 10/10/06, Will Glass-Husain [EMAIL PROTECTED] wrote:
Quick followup on this, then. Maybe we should leave the Avalon Log
Kit out of the velocity dependency jar?
My objective is to make this simpler for casual or new users. I'd
think at this point the Avalon approach doesn't add a lot
On 10/10/06, Nathan Bubna [EMAIL PROTECTED] wrote:
On 10/10/06, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote:
Nathan Bubna [EMAIL PROTECTED] writes:
lookup order: LogKit, Log4j, JDK logging, and StandardOutLogChute
(which sends error to Std.out and error to Std.err). This still
Alright, Nathan! Hack away!
WILL
On 10/10/06, Nathan Bubna [EMAIL PROTECTED] wrote:
On 10/10/06, Nathan Bubna [EMAIL PROTECTED] wrote:
On 10/10/06, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote:
Nathan Bubna [EMAIL PROTECTED] writes:
lookup order: LogKit, Log4j, JDK logging, and
Hi Llewellyn!
Good input. You're probably right in many cases. I did a quick scan
looking for Log.error. Many of them are initialization-related errors
-- perhaps those should be exceptions instead. We just moved the
app-level exceptions to be RuntimeExceptions which gives us more
freedom to
hey,
so you're sort of right about the reference errors, there are times for
both logging and erroring. and those times break down to development /
deploy. But as such, i still believe the default should be loud errors.
because if you are going to be silent, it's best to happen when
