Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 74189115C7 for ; Fri, 20 Jun 2014 14:09:25 +0000 (UTC) Received: (qmail 11595 invoked by uid 500); 20 Jun 2014 14:09:25 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 11544 invoked by uid 500); 20 Jun 2014 14:09:25 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 11530 invoked by uid 99); 20 Jun 2014 14:09:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jun 2014 14:09:25 +0000 Date: Fri, 20 Jun 2014 14:09:25 +0000 (UTC) From: "Remko Popma (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (LOG4J2-141) Documentation is lacking info about valid status levels MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-141: ------------------------------- Fix Version/s: (was: 2.0-rc1) > Documentation is lacking info about valid status levels > ------------------------------------------------------- > > Key: LOG4J2-141 > URL: https://issues.apache.org/jira/browse/LOG4J2-141 > Project: Log4j 2 > Issue Type: Bug > Affects Versions: 2.0-beta3 > Reporter: Joern Huxhorn > Assignee: Remko Popma > Priority: Minor > Fix For: 2.0-rc2 > > > http://logging.apache.org/log4j/2.x/manual/configuration.html#Configuration_with_XML > "The level of internal Log4j events that should be logged to the console." should contain a list of all valid status levels. > The same is the case further down the document at http://logging.apache.org/log4j/2.x/manual/configuration.html#StatusMessages > I understand that the StatusLogger is just a normal Logger so I assume that "trace", "debug", etc. are valid values - but I don't know and the documentation isn't telling me. > A list of all valid values, preferably quite at the start of the configuration documentation, would help a lot. -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org