Farr, Aaron wrote:
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED]
The site is under central - so just cd to anywhere more specific than avalon root and your building content at that level. For example - to build all of the runtime family:
$ cd avalon\runtime $ ant
Or, if you just want to rebuild utilities
$ cd avalon\runtime\util $ ant
Or, if you just want to rebuild i18n
$ cd avalon\runtime\util\i18n $ ant
Same priincipal applies everywhere.
Actually, now that I've looked at it, Javadocs are the real culprit. There's just so much source code to parse that generating javadocs takes a while. You can generate the site without javadocs by this:
$ ant init standard.prepare xdocs
though it would be nice if there were an easier way to build the site and not the javadocs. Perhaps a new target?
Just a the moment I'm not willing to say - thing is that the javadoc strategy isn't a done deal yet (or put it this way - I'm playing around with ideas as we speak concerning both x:install semantics and javadoc generation strategies). Should have some I can articulate more realistically sometime this weekend.
Steve.
J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
