Sorry I'm late to the party :) > -----Original Message----- > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > 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.
Excellent. > > 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. Excellent. The intent of Vindico is to use the Gump descriptors as the base to revive the great library of Alexandria. All of the modules on top of that would be great if they were pluggable. > > 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. Cool. > > -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. I am starting to like Vindico, but only recently. I was just about to jump ship again and build PyGump, to get away from building java code with java code, which started to drive me insane. Anyway, now I'm back, and I think Vindico is a great place to start to replace the dead Alexandria. The object model needs some more upgrades to handle the full Gump DTD, which it cannot right now. As a devil's advocate position, Vindico has one developer, whereas in recent weeks the Gump crowd has grown significantly. Haven't the developers voted with their feet already? Don't get me wrong, I do think Vindico is a better replacement for Alexandria, just have to ask the question. > > 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). OK > > 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. The major thing that I wanted to add to Gump and Alexandria functionality was a database recording some stats, but that is just fluff on top of everything else. The cron thing is a good idea, but I also wanted to be able to say 'just build turbine right now', and it would go off and do it. > > 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? It makes sense to me. Right now I am attempting to make Vindico work with unmodified Gump descriptors, and to also suport the full Gump DTD. Welcome to the party! Scott > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > -- > To unsubscribe, e-mail: > <mailto:alexandria-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
