-Mark
Stephen Colebourne wrote:
See the [collections] website for one way of doing this.
The main site is always bleeding edge. But, the navigation has explicit links to versioned javadoc. The maven xml grabs the cvs tagged code to create the additional javadoc. It seems quite neat (but then I did it...;-)
Stephen
From: "Mark R. Diggory" <[EMAIL PROTECTED]>
No, thats a really good point about versioned javadoc. Javadoc for version 1.0, 2.0, ..., Current of a subproject.
This would require maintaining the content of previous release site generations, pushing into a special directory reserved for its archiving.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
