[
https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884058#comment-15884058
]
Matt Sicker commented on LOG4J2-1807:
-------------------------------------
I feel that only a few major classes from log4j-core are meant to maintain
backwards compatibility. Really, as long as custom plugins can extend abstract
classes that always compile and link correctly, and as long as we keep the old
plugin factory methods from programmatic configurations, I think that covers
most of the expected classes. Really, anything that's documented in the manual
should maintain strict API compatibility where possible.
> [core] Add and implement LogEvent.toImmutable()
> -----------------------------------------------
>
> Key: LOG4J2-1807
> URL: https://issues.apache.org/jira/browse/LOG4J2-1807
> Project: Log4j 2
> Issue Type: New Feature
> Affects Versions: 2.8.1
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Attachments: logging-log4j2.patch
>
>
> [core] Add and implement LogEvent.asImmutable()
> {code:java}
> /**
> * Returns an immutable version of this log event, which MAY BE a copy of
> this event.
> *
> * @return an immutable version of this log event
> */
> LogEvent asImmutable();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
