[
https://issues.apache.org/jira/browse/MTOMCAT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999858#comment-13999858
]
Alex Wajda commented on MTOMCAT-127:
------------------------------------
I tried plugin versions 2.0, 2.1 and 2.2 and different approaches to route
logging to an alternative logging framework (e.g. log4j via slf4j):
http://stackoverflow.com/a/20476354/96766
http://stackoverflow.com/a/20476229/96766
and finally http://stackoverflow.com/a/11115274/96766
Neither worked.
> 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.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
