Hey Kevin,
If you put all of your tests into a Junit testsuite, and use the
<batch> paremeter of the <junit> task, junit will load the classpath
once and use it for all tests. Sometimes this isn't possible because of
dependency issues between tests, but give it a whirl.
/Dave
This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution
is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete
the message without disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption,
interception, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any
such corruption, interception, amendment, tampering or viruses or any
consequences thereof.
-----Original Message-----
From: Kevin Cline [mailto:[EMAIL PROTECTED]
Sent: 18 October 2006 00:16
To: user@ant.apache.org
Subject: path performance
I am working on a complex project with a LOT of JARs on the classpath.
Currently we are using this path element:
<path id ="classpath.unit_test">
<pathelement path="${test.config.dir}"/>
<pathelement path="${config.dir}"/>
<pathelement path="${config.xml.dir}"/>
<pathelement path="${classes.dir}"/>
<!-- add all files in lib.dir to path -->
<fileset dir="${lib.dir}">
<include name="**/*.jar"/>
<include name="**/*.zip"/>
</fileset>
</path>
This path is used in this junit element:
<target name="test" >
<junit >
<classpath refid="classpath.unit_test"/>
<test name="test1"/>
<test name="test2"/>
...
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
