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, then it will use the new StandardOutLogChute. On 10/10/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
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 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 will already not create a velocity.log > file unless Avalon LogKit or Log4j are available and a "runtime.log" > property is set. > - So killing the velocity.log file is as easy as not using > velocity-dep.jar and/or setting "runtime.log = " > - I know this only sort of a B.C. concern, but it isn't really a > trivial change either. > - I'm of the view that Std.err is for errors (and maybe warnings), > and is Std.out really redirected that often? And when it is, is that > really our concern? Seems to me anyone redirecting Std.out should be > prepared for surprises or least they shouldn't be critical. > > So, all that is to say that i currently am: > > -0 on removing Log4j and LogKit from the default lookup order in 1.5 > -1 on punting trace/info/debug messages to Std.err > +0 on punting warning messsages to Std.err > -1 on putting StandardOutLogChute or kin before JdkLogChute in the lookup order > +1 for tweaking this later on when we drop LogSystem support et al > > On 10/10/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > > Hi, > > > > As you can see with the log messages, we're making some headway on a > > variety of Velocity issues this week. > > > > One quick item for discussion. The default logging behavior is to > > create a file "velocity.log" in the current directory. This is really > > quite annoying in a webapp or integrated app. One of my colleagues > > built a quick email routine using Velocity in a webapp. Now, I see a > > "velocity.log" file created on my Linux server in whatever directory I > > happened to be in when I started Tomcat! > > > > Here's the suggestion. Switch the default logging to StdErr. I'd > > suggested something similar in VELOCITY-403, but there was no > > resolution. STDERR is preferred to STDOUT so that it doesn't mess up > > existing log files if out is redirected. > > > > Consequence... happier web developers. Possible problem - command > > line apps which depend on Velocity.log being created don't see it. > > > > Any comments? > > > > WILL > > > > -- > > Forio Business Simulations > > > > Will Glass-Husain > > [EMAIL PROTECTED] > > www.forio.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
