Thanks Ersoy for the link to the modeling tool. I have access to some
of them in IBM Rational App Developer and recall using some of their
primitive features. Though some intelligent software that auto
documents would be cool.
You've probably seen JAutodoc (Just for javadoc):
http://jautodoc.sourceforge.net/
One thing about pre-built tools and editors is that it can be tricky to fit
them into the build process. Personally when I want artifacts like diagrams
etc. generated I create an EMF model from annotated Java and then feed that
model through JET templates to generate further artifacts. This could be done
using a custom ant task for James.
EMF is what the rational tooling is built on, and now you have the flexibility to generate anything you want. Plus other James developers could just update the java interfaces describing the components and get the benefit of the automatically generated artifacts through the build process. This should make it fairly easy to get developers on board with maintaining the interfaces and corresponding annotations, since the effort is minimal.
The main thing I would shoot for is finding the common denominator in tooling
that everyone feels comfortable working with, since I'm sure you'd want to
contribute something that others will update as well avoiding stale
documentation, diagrams, etc.
Cheers,
- Ole
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
