On Wed, Apr 11, 2001 at 12:48:00PM +0200, Stefan Bodewig wrote:
> Your Supervisor class is loaded more than once. Singleton like
> patterns work only on a per classloader basis, that is you get one
> instance of your Supervisor per classloader.
[...]
> The only workaround I see is to put all necessary archives into the
> system classpath and don't define any classpath in your build file at
> all (neither for the java nor the junit task).
Hmm, that's a pity! It would be real dirty to include the classes to test into
ant's classpath because they're built with this build file. ... and because
other build files build other projects that may get confused seeing this
classes.
I now tried the diferent approach of having a second build file for the tests,
but that not as easy as that, either: I can't start an ant using that second
file with the ant-task, because the ant-task doesn't accept a new classpath.
Starting it with <java fork="false".../> results in an linkage error. But
using <java fork="true".../> finally worked.
Thanks again for your time, Stefan!
Gruesse, Kai
--
"Goodbye stranger, It's been nice, Hope you find your paradise" <Supertramp>
[EMAIL PROTECTED] + www.picturesafe.de
picturesafe GmbH, Lueerstr. 3, D-30175 Hannover fon:+49 511 85620 56
++ PGP Key fingerprint = D2 B9 58 DC 36 52 DB 6C 18 CC 43 9F 68 E0 21 97 ++
