Hmm..this raises an interesting issue. When you mention build dependencies, do you really mean build one project then another in the same process, or just that one project would depend on a jar from another? In the case of StrutsTestCase, 1) I don't like Core being dependent on a subproject, so perhaps another neutral mock library should be used, and 2) even if the Core build depended on StrutsTestCase, it would be the latter and use a jar.
As for the build organization, I lean towards 1, but I don't really feel strongly one way or another.
StrutsTestCase could easily be split into the mock servlet classes, and the testing framework itself. The latter could be included in the core package, and since the testing framework would depend on the core package, I think the dependencies would be satisfied.
-d.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
