[
https://issues.apache.org/jira/browse/LOG4J2-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-243.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta7
The includeLocation method is now protected. However, you may now simply set
the system property Log4jLogEventFactory to the name of the class to use to
create LogEvents.
These changes were added in revision 1487753. Please verify and close.
> LoggerConfig has a method that should be protected instead of private.
> ----------------------------------------------------------------------
>
> Key: LOG4J2-243
> URL: https://issues.apache.org/jira/browse/LOG4J2-243
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-beta6
> Reporter: Kurt Lehrke
> Priority: Minor
> Fix For: 2.0-beta7
>
>
> LoggerConfig has a protected constructor that has an argument called
> includeLocation (boolean). When log4j2 calls this constructor they use the
> private static boolean includeLocation method to determine this argument.
> Since it's private, I cannot call it. I would like to suggest this to be
> changed to a protected method instead. That way, I don't have to duplicate
> the method in order to call this constructor, especially since it's
> specifically for the protected constructor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
