You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/03/18 21:21:33 UTC
[jira] [Commented] (LOG4J2-1323) Remove Final Declarations on Many
Classes/Methods
[ https://issues.apache.org/jira/browse/LOG4J2-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202078#comment-15202078 ]
Ralph Goers commented on LOG4J2-1323:
-------------------------------------
Can you provide some examples of the kinds of customizations you have had to do? If possible I would prefer to build more flexibility into what is there instead of resorting to having to extend classes.
> Remove Final Declarations on Many Classes/Methods
> -------------------------------------------------
>
> Key: LOG4J2-1323
> URL: https://issues.apache.org/jira/browse/LOG4J2-1323
> Project: Log4j 2
> Issue Type: Wish
> Components: API, Appenders, Pattern Converters
> Affects Versions: 2.5
> Reporter: Andrew Bernhagen
> Labels: architecture, easyfix, newbie, patch
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Within my organization, I've had to develop a custom appender that automatically configures certain properties and a specific layout to tie into other initiatives we have tied to logging. Log4j2 made this much more difficult than Log4j1 due to the use of final on many classes (e.g. the appender implementations) and methods (all pattern layout methods). This has made extension overly difficult and filled with a lot of copy and paste that I'd rather not have. Is it possible that these could be removed to make it easier to extend the existing implementations?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org