Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Date: Thu, 26 Sep 2013 13:58:03 +0000 (UTC)
From: "Xavier Dury (JIRA)" <jira@apache.org>
To: dev@tomcat.apache.org
Message-ID: <JIRA.12546553.1331805718985.24202.1380203883481@arcas>
In-Reply-To: <JIRA.12546553.1331805718985@arcas>
References: <JIRA.12546553.1331805718985@arcas>
Subject: [jira] [Comment Edited] (MTOMCAT-127) tomcat:run - Configuring
 Logging with JULI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MTOMCAT-127?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137=
78796#comment-13778796 ]=20

Xavier Dury edited comment on MTOMCAT-127 at 9/26/13 1:56 PM:
--------------------------------------------------------------

Same problem here: I'm trying to use a custom logging.properties through <t=
omcatLoggingFile /> in order to use SLF4J jul-to-slf4j bridge but it doesn'=
t work (logs are not forwarded to SLF4J).
               =20
      was (Author: kalgon):
    Same problem here: I'm trying to use a custom logging.properties throug=
h <tomcatLoggingFile /> in order to use SLF4J jul-to-slf4j bridge but it do=
esn't work (logs are still forwarded to SLF4J).
                 =20
> tomcat:run - Configuring Logging with JULI=20
> -------------------------------------------
>
>                 Key: MTOMCAT-127
>                 URL: https://issues.apache.org/jira/browse/MTOMCAT-127
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: New Feature
>          Components: tomcat6, tomcat7
>    Affects Versions: 2.0
>            Reporter: C=C3=A9dric Couralet
>            Assignee: Olivier Lamy (*$^=C2=A8%`=C2=A3)
>            Priority: Minor
>             Fix For: backlog
>
>
> The configuration for a custom logging.properties is not taken into accou=
nt with the tomcat6-7:run goal.
> From what I've seen, the reason is that the configuration for java.util.l=
ogging is done before setting the system properties in the same class loade=
r.
> I think it could be fixed by putting a call to LogManager.getLogManager()=
.readConfiguration(); right after setting the system properties. I'm not co=
nfident enough on the possible side effects to say it is the best solution.=
=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org