[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60116 ]
Jesse Kuhnert commented on MSUREFIRE-69: ---------------------------------------- No I think you're right, I just think it's something I'm not completely in control of. TestNG tries very hard to provide defaults that do have outputs. The new constructor seemed to be the only option without wildly changing other things internal to testng. I've made it so that setUseDefaultReports ( false ) works for the most part, but am not completely sure that html output won't still be generated with this alone. Perhaps me figuring out how to make my local repo use my surefire code changes will solve my dilemna. I wasn't having any problems getting the surefire stuff to use the new testng code, it was problems getting the new surefire code to be used by testing in general. > 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]
