<snip/>
It seems to me that a framework which ships (and supports) a ready-made set of mock classes will have an advantage in today's world.
Yes. It's interesting how things work out. Over the years I used to swear by in-container based test suites, but after fighting with Cactus and fiddling with a few others I have a new appreciation for Mock vs. in-container testing.
Aren't there already Mock test frameworks out there that we can use? I mean, why reinvent the wheel? I could see a problem if the license were incompatible. Your thoughts?
<snip/>
FWIW, in retrospect, I see that I chose "core-library" in both faces and shale. Might be worth considering.
You mean name the jar produced by struts/current/core/ as "core-library-x.y.z.jar" ?
That seems a bit ambiguous doesn't it? I mean, core library for what? Wouldn't that be confusing having a naming clash with Shale?
<snip/>
Craig
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
