From: Dan F. (JIRA) <ji...@ma...> - 2007-07-16 18:35:28
|
[ http://jira.public.thoughtworks.org/browse/CC-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_14712 ] Dan Fabulich commented on CC-542: --------------------------------- -uselogger definitely *doesn't* support multiple listeners. That means that when you have to use -uselogger, you're forced to make a difficult choice between log4j and breaking the standard built-in XmlLogger that CC needs to track the build logs internally. That's why multiple listeners should be officially supported in CC (again, patch submitted); the official way to use log4j should be through adding it as an additional listener. > (PATCH) Provide support for configuring additional Ant listeners > ---------------------------------------------------------------- > > Key: CC-542 > URL: http://jira.public.thoughtworks.org/browse/CC-542 > Project: CruiseControl > Issue Type: Improvement > Components: Core Application > Affects Versions: 2.6 > Reporter: Dan Fabulich > Assigned To: Jeffrey Fredrick > Attachments: 2704listenerconfig.patch > > > Currently you can set JVM args and system properties for Ant, but you can't attach additional listeners to Ant. > http://ant.apache.org/manual/running.html#options > http://ant.apache.org/manual/listeners.html > Without this, there's no good way to get the Ant build to log to log4j. This wiki article provides a hacky suggestion to include the other command-line arguments in the "target", exploiting the fact that CC will simply append those arguments as if they were targets. This is a bad way to do a very good thing. > http://confluence.public.thoughtworks.org/display/CC/Log4jAndCruiseControl > Instead, the <ant> schedule should have a <listener> attribute that you can configure in addition to the regular XmlLogger CC uses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |