[jira] [Closed] (LOG4J2-1823) Remove deprecation on MessageSupplier lambda functions in Logger API

["Matt Sicker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker closed LOG4J2-1823.
-------------------------------
    Resolution: Fixed

Changed in master.

> Remove deprecation on MessageSupplier lambda functions in Logger API
> --------------------------------------------------------------------
>
>                 Key: LOG4J2-1823
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1823
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.6
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>             Fix For: 2.8.1
>
>
> The changes done in LOG4J2-1286 to deprecate MessageSupplier were not properly tested in practice. Using log4j-api ever since the deprecation, the following code causes deprecation warnings:
> {code}
> logger.info(() -> new SimpleMessage("Hello, world!"));
> {code}
> This is because the compiler interprets this as a {{MessageSupplier}} instead of the more generic {{Supplier<Message>}} version which is the intended API. Although manual use of {{MessageSupplier}} should be discouraged, users should not have to manually cast the above lambda just to prevent a deprecation warning:
> {code}
> logger.info((Supplier<Message>) () -> new SimpleMessage("Hello, world!"));
> {code}
> {{MessageSupplier}} should become a normal part of log4j-api with a note on both it and {{Supplier<T>}} that these interfaces would be removed in a log4j-api 3.0 release and replaced with the Java 8 version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org