DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20791>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20791 [PATCH] add support to <junit> for popping up the JUnit GUI ------- Additional Comments From [EMAIL PROTECTED] 2003-06-19 10:40 ------- This is totally overloading the <junit> task. There's a dozen of attributes that are ignored in GUI mode. Nested <formatter>s are ignored, fork is always true, etc. Effectively, this is another task. [Note: while Ant has a tradition of heavily overloading tasks, such as <available> and <property>, it's not something that should be followed IMHO]. I wonder what the 'uimode' gives you that cannot be easily done by just using <java classname="junit.swingui.Runner">? Is it the specification of the tests to run via <test>/<batchtest>? The classpath configuration? I'd rather see this added to a separate task, say <junitgui>. In that context, it would make sense to refactor the JUnitTestRunner class (and others) so that it can be more easily reused from other tasks. However, I doubt that a GUI-based task would be included in Ant anyway. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
