Since this describes the site I work on, I wrote an ant task that will record and re-create symlinks using properties files. So if you go this route you may (or may not) want to check it out ant's <symlink> task and set up some scripts or targets to maintain this information. However, this may not be as neccessary because in your case, there are one or more people for each sub-section that can probably manually maintain a few such links each. In my case I have over a dozen sections and there is just one of me so I automate it :).
-Gus
robert burrell donkin wrote:
On 7 Feb 2004, at 21:32, Mark R. Diggory wrote:
robert burrell donkin wrote:
On 7 Feb 2004, at 20:53, Mark R. Diggory wrote: <snip>
It also gives developers some room to work. If there is a global nightly/weekly process for generating the commons site and its sub-projects then in reality they probibly don't want the site xref/xdocs generated off of thier bleeding edge all the time.
hmmm...
i'd probably want the best of both worlds - the latest and greatest version but also versions of the site for each release. i suppose that it'd be possible to do something with directories so commons/kool/current would contain the latest version but commons/kool/7.12.89/ would contain the documentation which was current when 7.12.89 was released.
just a suggestion (rather than a criticism)...
- robert
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.
craig advocated something similar in the original commons release documents (but only kept the last release). it shouldn't be too great a burden to copy the current website into a specially numbered directory when a release is cut.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
