: > Yeah, that would be one thing -- different classpaths/ vm properties : > etc. This could be problematic. : : The Python runner completely cheats here, which is bad (because we may : pick up a dep we didn't intend to, and never catch it)... just takes : the union of all CLASSPATHS.
as long as the default "ant test" does recursive testing of "ant test" in the individual modules with their isolated classpaths to ensure no dependency bleedover, a special case top level "ant run-all-tests-parallel" target that unions all hte classpaths seems like it might be acceptible for things like continuously randomized test only jenkins builds. but i wonder if reproducibility might be a problem? if you don't get the same classpath, and some classes are loaded i na diff order, would you be able to "cd modules/foo && ant test -D..." and see the same failures? -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
