Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-243

LoggerConfig has a method that should be protected instead of private.

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta6
    • Fix Version/s: 2.0-beta7
    • Component/s: Core
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kurt.lehrke Kurt Lehrke
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: