I think it'd be interesting to get a JDepend report into our framework build process. That would help us identify problems with the current package structure as well as with any structure we'll be moving to.
It's pretty easy to do (even without using Maven ;-) ), and I'd give it a shot when a find some spare hours. What do you think?
Vincent Massol wrote: [snip lots]
Indeed, there are several options:[snip lots more]
1/ o.a.c.client.servlet and o.a.c.server.servlet 2/ o.a.c.servlet.client and o.a.c.servlet.server 3/ o.a.c.servlet
but then there are lots of other support classes like: AbstractClientTestCase, AbstractWebClientTestCase, AbstractWebServerTestCase, etc.
where do we put these? I wanted to put them in o.a.c.testcase:
o.a.c.testcase o.a.c.testcase.servlet o.a.c.testcase.jsp [...]
As you mention, there are 2 functional aspects: Servlet/JSP/etc vs TestCase/Redirector/Connectors/etc. ATM, I was more following the later route (i.e. functional WRT what the class does) rather than the former (i.e. functional WRT a test domain).
-- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
