I think the best solution to this now would be to put the mock classes back under core test and simply build them as a separate jar (so taglib and tiles can use them).
Do you agree?
If mock were simply included in struts-core.jar, then taglib and tiles could also use them.
Furthermore, everything which would ever depend on struts-mock would also depend on struts-core.
I propose including them in the regular core distribution for simplicity. Put them in the same repository as everything else that goes in core: src/share. What's a few hundred kb or less of extra weight in there? I just feel like every argument to do anything else makes things more complex for little more than formalistic gain.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
