Conor
You're a star!!!, but to be honest, I'm still slightly confused.
${ejbjar.generic.destdir} is infact ${lib.dir} (which is a directory and not
a specific file). Prior to building the ejbjar, other standard class jars
are built and stored in ${lib.dir}. Thus before building the ejbjar, other
classes get compiled with a classpath containing any jar in ${lib.dir}. But
what I dont undertstand is, why would a compilation of a standard class even
go near any ejbjar jar file in ${lib.dir} and thus "lock" it for a while?
There's nothing in there that it needs, but rather the compiling class would
require classes for other standard class jar files in ${lib.dir}, which is
fine.
Any how to resolve this, I've partitioned the lib dir into two sub
directories, an ejb directory for ejb jar files and a common directory which
contains standard class jars.
I think I've alot to learn about the internal workings of java, ant
etc...!!!
PS: that path element. when runing ant, the directory in the fileset MUST
exist before ant will run. It would be great if I could specify a directory
that gets created once ant runs?
-----Original Message-----
From: Conor MacNeill [mailto:[EMAIL PROTECTED]]
Sent: 09 February 2001 14:02
To: [EMAIL PROTECTED]
Subject: Re: weblogic ejbjar creation failure
Mick,
The crucial question now is where does ${ejbjar.generic.destdir} point and
is it included in a classpath used for a compile or for ejbjar. If so, and
a class is loaded from it, the compiler class (in Ant's VM) will obtain a
lock on the jar which it won't release "for a while"
Conor
