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=10413>. 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=10413 enhancement: JUnit task only creates one forked VM per batch Summary: enhancement: JUnit task only creates one forked VM per batch Product: Ant Version: 1.4.1 Platform: All URL: http://www.servidium.com/demo/ttemp/rfwan/antcustom OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently, running the JUnit task with a forked VM and a batchtest causes a new VM to be spawned for EACH file in the fileset. For large projects, this causes a severe slowdown as expensive "setup" opertions are performed repeatedly. At the above URL, can be found a GroupedJUnitTask and a DynamicTestSuite (inside the antcustom-src.zip) which extends JUnitTask and uses only one VM per batch rather than one VM per item in the batch. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
