[infinispan-issues] [JBoss JIRA] (ISPN-2107) Enable logging for all modules' test suites
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Jun 12 11:30:04 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700814#comment-12700814 ]
Galder Zamarreño commented on ISPN-2107:
----------------------------------------
Btw, as mentioned to Dan yesterday, to get each component to log to a separate file, we could use a similar trick to what's suggested in ISPN-2042.
> Enable logging for all modules' test suites
> -------------------------------------------
>
> Key: ISPN-2107
> URL: https://issues.jboss.org/browse/ISPN-2107
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 5.1.5.FINAL
> Reporter: Dan Berindei
> Assignee: Mircea Markus
> Fix For: 5.2.0.ALPHA1
>
>
> Some modules do not log anything, not even to the console, because they don't have a {{log4j.xml}} file in their classpath (e.g. cdi). Because of this, errors in jenkins are harder to spot and to fix.
> We should ensure that each module has a log4j configuration file in the test classpath (or maybe use a system property to configure a generic log4j.xml in the root directory). Preferably each module should have its own log file, but they could use the same log file as long as they don't truncate it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list