If I remember correctly this was added on request of a user.
They did not want to set the StringFormatterMessageFactory when obtaining a
Logger because that would force them to use the printf format everywhere.
If I remember correctly the use case was that they wanted to use the
"message {} with {} params" in most cases but sometimes it was desirable to
use the printf format with its more fine-grained control over the output
format.
Ralph agreed that this would be a useful feature and made the change.On Sat, Feb 8, 2014 at 1:51 PM, Gary Gregory <[email protected]> wrote: > I think it has something to do with making it easier to port call sites > from: > > System.out.println(...) > > and > > Console.printf(...) > > I do not think reusing these API names in Logger is a good idea though. > > I'd like to remove them. > > Gary > > > On Fri, Feb 7, 2014 at 10:18 PM, Nick Williams < > [email protected]> wrote: > >> Yes, I'm confused by this addition to. Why did we do this? >> >> Nick >> >> On Jan 30, 2014, at 12:24 AM, Gary Gregory wrote: >> >> I'm slightly confused by this addition because it seems redundant with >> using StringFormattedMessage and StringFormattedMessageFactory >> >> Gary >> >> -- >> 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 >> >> >> > > > -- > 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 >
