ok. I'm not sure whether recreating the classloader for each test is
really necessary though, but we can look into it.
Is this something you can correct by some appropriate commands in
tearDown() ? It seems that would be more robust across test runners (I'm
not sure how IDEs handle your tests, for example).
- Brett
Wendy Smoak wrote:
(resending from the right address...)
From: "Brett Porter" <[EMAIL PROTECTED]>
What forking are you using in m1/ant?
None. Or rather, whatever the default is-- I have nothing in
project.properties that says otherwise.
Likewise, nothing special in the surefire configuration in pom.xml, so I'm
using the defaults there, too.
I've tracked the difference down to the fact that with m1/Ant, you get a
new
AntClassLoader for each test case, while with Surefire, you keep the same
IsolatedClassLoader throughout the tests.
I don't _think_ I'm forking a new JVM because I'm able to step through the
entire set of tests in JSwat (debugger) in both m1 and m2.
Suggestions?
Thanks,
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
