While working on the documentation of the junitlauncher task, for fork support, I realized that when we first released this task, due to an oversight, I did not add support for setting system properties or environment variables through this task. The fork element now supports that[1] in the upcoming release, so that the forked JVM can be configured with system properties and/or environment variables.
I am thinking of adding this support for even non-forked execution, like junit task does. However, I would like some inputs on whether such support for setting the system properties in a non-forked execution should be at the junitlauncher task level or whether it should be configured within each <test> and <testclasses> level. Or should we allow it to configured at the task level as well as the individual <test>/<testclasses> level? junit task currently does it only at the task level. [1] https://github.com/apache/ant/commit/ffb80b688a12d4e60ab4be466ec0b3e396bb0078 -Jaikiran --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
