Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Wed, 8 May 2013 15:39:15 +0000 (UTC)
From: "Kurt Lehrke (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12646640.1368027470956.288004.1368027555854@arcas>
In-Reply-To: <JIRA.12646640.1368027470956@arcas>
References: <JIRA.12646640.1368027470956@arcas>
Subject: [jira] [Created] (LOG4J2-243) LoggerConfig has a method that should
 be protected instead of private.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kurt Lehrke created LOG4J2-243:
----------------------------------

             Summary: 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


LoggerConfig has a 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.

--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org