> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 30, 2003 1:57 AM
> To: Avalon framework users
> Subject: Re: Merlin Dynamic Block Un/Loading
>
>
> Olaf Bergner wrote:
>
> >I played around a bit to find a minimal setup for reproducing the
> >LinkageError. To this end, I reused an existing block of mine to
> be deployed
> >via AMTC.
> >
>
> AMTC - that would be  ...
>
>      "Automated Magic, Tricks and miscaleneouse acts of Concealment"
>
> :-)
>
> >This is what does the trick:
> >
> >(1) Subclass AbstractMerlinTestCase
> >
>
> no problem here
>
> >
> >(2) Add two (>1) *empty* test methods, don't overwrite setUp()
> or tearDown()
> >
>
> ok
>
> >
> >(3) Run the test case
> >
>
> done
>
> >
> >(4) First test method runs just fine
> >
>
> yep
>
> >
> >(5) Second test method fails during setUp()
> >
>
> Not in my example
> Take a look at avalon-sandbox/merlin-test/hello
> It has to be something else.
>

You are right: it has to be something else. I took your template project,
tweaked merlin.properties a bit and added avalon.properties so that
everything builds just fine and StandardTestCase passes. Then I added an
empty test method to StandardTestCase. Works like a charm, absolutely no
problems. Merlin shuts down and restarts just fine. Now what's going on
here? I don't get it. Did you notice something special about Fernando's
setup?

Anyway, it's getting late here in Germany. I'll call it a night and put this
mistery back on the shelf, right next to my monograph about unsolved
problems in superstring theory.

> Stephen.
>

Take care,

Olaf


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to