[LOG4J2-2947] LogBuilder should not have no-op default methods

• Type: Wish
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.14.1
• Assignee: Unassigned
• Reporter: Marcono1234
• Created: 18/Oct/20 20:02
• Updated: 01/Mar/23 06:53
• Resolved: 05/Mar/21 06:24

Description

Currently the methods of the interface org.apache.logging.log4j.LogBuilder are all default methods which are no-op.
In my opinion this is not ideal because these no-op implementations should only exist for the LogBuilder.NOOP, or for any methods which are added in the future which not every logger supports.
With the current situation it is easy to forget implementing one of the LogBuilder methods.

If you choose to keep this LogBuilder behaviour, it would be good to at least document this so implementors of the interface are aware of it. Though this would then create confusion for the end-user because the LogBuilder returned by Logger is actually not no-op (which also shows that the LogBuilder methods should not be no-op by default in the first place).

Issue Links

• fixes: LOG4J2-3033 LogBuilder don't require a message
• links to: GitHub Pull Request #1051