[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-tabpanelfocusedCommentId=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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[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-tabpanelfocusedCommentId=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/5274/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
[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-tabpanelfocusedCommentId=13999844#comment-13999844 ] Alex Wajda commented on MTOMCAT-127: I am also voting for resolving the issue. We use embedded Tomcat for our integration testing on TeamCity which parses the build log, extracting errors and warnings in Log4J format, but it doesn't seem to understand the java logging output format. It would be very helpful to be able to customize the Tomcat output for better integration with different (not just TeamCity) automated building tools. 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
[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-tabpanelfocusedCommentId=13906774#comment-13906774
]
Xavier Dury commented on MTOMCAT-127:
-
I aslo tried to define java.util.logging.config.file properties with:
systemProperties
java.util.logging.config.file${project.basedir}/src/main/config/tomcat/logging.properties/java.util.logging.config.file
/systemProperties
but my configuration seems to be overridden in class AbstractRunMojo:
System.setProperty( java.util.logging.config.file, new File(
configurationDir, conf/logging.properties ).toString() );
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.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[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-tabpanelfocusedCommentId=13778796#comment-13778796 ] Xavier Dury commented on MTOMCAT-127: - Same problem here: I'm trying to use a custom logging.properties through tomcatLoggingFile / in order to use SLF4J jul-to-slf4j bridge but it doesn't work (logs are still forwarded to SLF4J). 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[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-tabpanelfocusedCommentId=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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[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-tabpanelfocusedCommentId=13697693#comment-13697693 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-127: do you have any sample project? 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
