I want to use what remains of the Alexandria infrastructure to run the
javadoc doclet, umldoclet, javasrc, checkstyle and jdepend and put it all
together.
Currently these features are in Centipede, but we would like to
1. Make them work with the Gump-Vindice-Alexandria descriptors
2. submit all this as patches to Alexandria proper
3. Give Alexandria a life of it's own by concentrating on the code
documentation-comprehension part. Basically Megaenhanced Javadocs, with
integrated uml, metrics, and source.
The code is there to be submitted-donated, we just need to understand how to
make it run on a workspace in a nice way.
-oOo-
We took a deep look at both Gump and Vindico.
Personally I like Vindico much better for _this_ task, since it's all Java
based and has a more complete objectmodel.
Given that Gump+Vindico+Centipede+Maven+thenextbigthing would benefit from
having a /common/ system of running against a workspace definition, what
could this system be?
Let's call this Vindico for now, (which seems to get closest to this).
We could have Gump (builds) Alexandria (code documentation) Forrest (site
creation) and Maven (for site creation and metrics, since build is done by
Gump) be used as plugins to Vindico, which in turn becomes a Workspace cron
system, with a consistent way of dealing with "nags" or messages.
This could also mean that we could plugin 2 instances of Gump: one for
builds with versioned jars, one with the latest.
What do you think, does it make sense?
What do you guys think I can do to get the code documentation features up
and running with Alexandria?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
