Unit tests should not really take to much time... and thus should not
really be turned off. Tests may need to be revisited to improve the
speed, or split them off into unit and integration tests (easy to do
with TestNG using groups).
Also, not sure what the fork mode is set to currently for OpenEJB,
but if you can, use "once" to only spin off one jvm for the entire
flight of tests. Using "pertest" will slow things down significantly.
--jason
On Nov 29, 2006, at 12:09 AM, Jacek Laskowski wrote:
On 11/29/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
OpenEJB 2 (2.2 or 2.3) will not build due to test failures in
"OpenEJB :: Builder":
Whoops! It's probably me who broke it. I intentionally turned off the
tests to speed up the build and incidentally introduced the failures.
Dave J. has proposed to comment out the respective tests in OpenEJB
that seem to be the culprit, so at least one possible solution already
exist. I should have it fixed soon.
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl
