I didn’t realize the requester had created a Jira issue. I fixed LOG4J2-2947 last night and included the log() method as I remembered seeing the request. So I guess I just need to add this issue to changes.xml.
Ralph > On Mar 5, 2021, at 8:18 AM, Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > > This sounds like a legit request to me. Isn't it just a matter of > introducing a LogBuilder#log() method to the interface and implementing it? > If it is that simple, I can give it a shot. > > ---------- Forwarded message --------- > From: Caleb Cushing (Jira) <j...@apache.org> > Date: Mon, Mar 1, 2021 at 7:23 PM > Subject: [jira] [Created] (LOG4J2-3033) LogBuilder don't require a message > To: <notificati...@logging.apache.org> > > > Caleb Cushing created LOG4J2-3033: > ------------------------------------- > > Summary: LogBuilder don't require a message > Key: LOG4J2-3033 > URL: https://issues.apache.org/jira/browse/LOG4J2-3033 > Project: Log4j 2 > Issue Type: New Feature > Reporter: Caleb Cushing > > > So based on the documentation, it looks like when you use a LogBuilder that > a message is required. I personally set throwable only logging messages to > `""`. It'd be nice to not have to set one. maybe this. > > ``` > logger.atError().withThrowable(exception).log(); > ``` > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005)
