DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32975>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32975 Summary: Make XmlFormatter for junittask (optinally) lighter Product: Ant Version: 1.6.2 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: blocker Priority: P2 Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] BugsThisDependsOn: 32973 The xml formatter (needed for the junitreport task) adds for each testcase all ant properties to a xmlfile. In a project with a substantial amount of ant properties this can lead to a big file. Combined with a lot of testcases this results in megabytes of property information that are all the same. Since i don't know anybody who actually uses this information, it might be a good idea to make the generation of property information by the xml formatter optional. Something like a 'includeProperties' property or a 'verbose' property could be nice. It would also make the processing of the junitreport task a lot faster. Just a small example: In our project, we added a custom formatter that does the same as the default xml formatter but removes the properties. It brings the overall size of the test.xml files back from 17 meg to under 1 megabyte. Xslt transformtion is ofcourse a lot faste -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
