> > what about using Docbook for documenting things? > > I can't comment on that as I don't know docbook. Any thoughts from others? I was thinking about a developer manual: * your general structure, the invocation infrastructure, the fact that components are active objects...and so on. > > > Another thing: I a graph of dependency between modules will help new > > developers to inspect better the code. > > Good idea. Are you looking for a module dependency graph (we can > probably get the info from Maven) or class dependency graphs?
A statical view of your project. For example: if this module depends on this and why. So one can inspect the module and see the relations on modules. Well, I'm writing some docs about Tuscany right now in Italian for the behavioural skeleton [1] over Tuscany, which i've created a while ago. So pretty busy. Cheers, Giorgio. [1] http://www.di.unipi.it/~aldinuc/papers/2007_beske_cg_crete_book.pdf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]