On 10/18/06, Kevin Cline <[EMAIL PROTECTED]> wrote:
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 sound
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
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 in ${lib.dir}, it's unlikely it's the fileset scan
that's taking so
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
ereof.
-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 el
apache.org
Subject: path performance
Importance: Low
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
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:
