Thank for pointing out your work.
The lack of Javadoc makes it hard to understand what the builder does or
what is the intent of its scope. For example:
builder.addAppender(extraAppenderName,
"myapp-extra.log", "myapp-extra.log.%d{yyyy-MM-dd}");
Does that always create a rolling file? What if I want to log to a
simple file? Or logging to the console? To a database?
How broad is the builder supposed to be?
Is there a way the Core's config code could be made better to either
make this builder redundant or easier to write?
Thank you!
Gary
On Mon, Mar 2, 2015 at 7:01 AM, Behrooz Nobakht <[email protected]> wrote:
> Hi,
>
> It's been a while that I've been using Apache Log4j 2 using no
> configuration file.
> This is quite useful in the context of embedded services and small
> application.
> Basically, all the configuration is done via code and using standard
> Apache Log4j API.
>
> I thought it might be good to extract a very small module to present how I
> have done this so far.
> The result is available at
> https://github.com/nobeh/log4j-configuration-builder
>
> I'd be happy to work on it further as a contribution to the core library
> and consider
> it to be merged into the library. I'd appreciate your feedback and
> thoughts on this.
>
> Thanks,
> Behrooz
>
>
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
