I would like to run xmlvalidate over a number of fails, and have it validate
all files even if some validations fail, but terminate the build when some
validations do fail. Setting failonerror=false solves half the problem.
Any clues about solving the other half?
I have noticed the same thing. Which version of Junit are you using?
On 12/19/06, Matt Benson <[EMAIL PROTECTED]> wrote:
Has anyone ever noticed Ant running junit tests
exceedingly slowly, perhaps only in the case of
testsuites or nested testsuites? I am looking at a
testsuite that has about
Put a subject on the message.
On 11/15/06, Tom Corcoran <[EMAIL PROTECTED]> wrote:
I raised this before there was no comment. I need to change my
subscription to my gmail account but I get the bounce below. Please is
their any way I can change my membership to use gmail?
Thanks, Tom.
Deli
Running unit tests via the Ant junit task seems to be extraordinarily slow.
For example, I have one test that runs in 24 seconds if I start it via "java
junit.textui.TestRunner" but it takes over three minutes to run the same
test via the ant junit task. Truss shows that the junit execution examin
On 10/18/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Timing indicates that ant is spending 30 seconds per test to walk the
lib
> tree building the classpath. Does anyone have a solution to this
problem?
Frankly, that sounds a bit fishy ;-)
Unless your hierarchy is
exceedingly large
On 10/18/06, David Corley (AT/LMI) <[EMAIL PROTECTED]> wrote:
Hey Kevin,
If you put all of your tests into a Junit testsuite, and use the
paremeter of the task, junit will load the classpath
once and use it for all tests. Sometimes this isn't possible because of
dependency issues betwe
I am working on a complex project with a LOT of JARs on the classpath.
Currently we are using this path element:
This path is used in this junit element:
