Re: Logging configuration

+1 for logical names and a configurable base. On Fri, Nov 11, 2016 at 6:24 AM, Claude Brisson wrote: > In fact, the logger name (well, *base* logger name) is configurable. So we > can both be happy: we can have the default base logger name be > "org.apache.velocity", as like

Re: Logging configuration

In fact, the logger name (well, *base* logger name) is configurable. So we can both be happy: we can have the default base logger name be "org.apache.velocity", as like you say it is more intuitive, and people like me willing to shorten it can still tune their config file. But as I said, I'd

Re: Logging configuration

Doing only casual debugging, as long as its intuitive to set the debugging name="foobar" name without having to dip into the code sounds great. The package name is however the easiest to remember as its from the class you are trying to debug (using attached source jar). Thanks On 11 November

Re: Logging configuration

And also velocity.rendering for every rendering error (including introspector/uberspector). So here's the new list: - velocity for the app/runtime/singleton - velocity.event for the event cartridge - velocity.directive, and velocity.directive.[directivename] - velocity.parser -

Re: Logging configuration

Why not, but it should be done right now to take advantage of the major version change. I checked quickly, and it seems like all logging backends build the loggers hierarchy using namespaces separated with dots, which can be class names by convention but it is not at all necessary. I'd