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

["Pablo Karlsson (JIRA)" <ji...@apache.org>]

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

Pablo Karlsson commented on MTOMCAT-127:
----------------------------------------

I have the same problem. It would nice to see this fixed because since tomcat 7 all jars are Scanned for TLDs by tomcat and logging of which jars that has been scanned would help a lot in determining witch jars to skip in this scan.
                
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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