You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Constantino Cronemberger (JIRA)" <ji...@apache.org> on 2015/03/20 20:16:39 UTC

[jira] [Commented] (MTOMCAT-127) tomcat:run - Configuring Logging with JULI

    [ https://issues.apache.org/jira/browse/MTOMCAT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371893#comment-14371893 ] 

Constantino Cronemberger commented on MTOMCAT-127:
--------------------------------------------------

workaround I have used was:

mvnDebug tomcat7:run -Djava.util.logging.config.file=src/test/resources/logging.properties

> tomcat:run - Configuring Logging with JULI 
> -------------------------------------------
>
>                 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édric Couralet
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Minor
>             Fix For: backlog
>
>         Attachments: mtomcat-127.zip
>
>
> The configuration for a custom logging.properties is not taken into account with the tomcat6-7:run goal.
> From what I've seen, the reason is that the configuration for java.util.logging is done before setting the system properties in the same class loader.
> I think it could be fixed by putting a call to LogManager.getLogManager().readConfiguration(); right after setting the system properties. I'm not confident enough on the possible side effects to say it is the best solution. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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