Add -Dnojars=true during the run of the single test and zero compilation time is the
result.
Add -Djbosstest.nodeploy=true and you can also avoid having to deploy the tests
into the server. I routinely run single tests in 10 seconds with these options.
Refactoring
the entire testsuite for a simple usage problems is silly.
Breaking up the huge monolithic build file into seperates test files would be a good
thing.
This is what we had in 2.4 and it was nice when we had < 200 tests. Now as we
approach 1000 its time to revisit this as well.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 19, 2002 2:55 PM
Subject: Re: [JBoss-dev] Build System... any ideas
> They'd probably solve the problem of 7 minutes to build to run a single
> test that I experience.
>
> Moving stuff to module specific test dirs would be a lot of work. I wonder
> if instead we could make dir-specific generic build targets -- something
> like in ${test.module} run xdoclet, compile all classes, then run jar for
> ${test.module}, then run tests in that module also. Sort of like "test"
> but limiting the xdoclet and jar tasks also.
>
> The build file is getting so large this might help make it more
> comprehensible also.
>
> david jencks
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development