[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60113 ]
Jesse Kuhnert commented on MSUREFIRE-69: ---------------------------------------- Hi Brett, The use of that method is decieving in it's current form. The default no args constructor creates a default listener for html reporting output. After that, setting the defaultListeners boolean flag is problematic because you have no idea what in the local list are defaults and what are things people have added. I would like to take out the setter altogether but haven't as I'm not sure if it's used by others. The new constructor with a boolean arg should fix our problems. I also re-factored the suiterunner to not add a bunch of others by default (ie the xml/txt outputs, which are our biggest problem). So, this should be fixed by using testng from the latest cvs head. I've tried testing it locally but for some reason doing a mvn install of surefire isn't causing my local repo jars to be used. It could be that the surefire plugin is explicitly using a particular version of surefire that takes precedence over my local build? > stop output to test-output directory > ------------------------------------ > > Key: MSUREFIRE-69 > URL: http://jira.codehaus.org/browse/MSUREFIRE-69 > Project: Maven 2.x Surefire Plugin > Type: Sub-task > Reporter: Brett Porter > Fix For: 2.2 > Attachments: surefire-patch.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
