Stephen McConnell wrote:
- we keep avalon.apache.org/api/ where it is
Have just encountered a problem while updating the James buildfile.
There does not appear to be any easy way get to the individual javadoc packages. If I select the framework and click on API I get the entire Avalon suite. Same problem occurs when you hit the API link for Phoenix - instead of Phoenix APIs you get all of Avalon. This isn't really what you want to direct users to if you simply want to throw up a particular product API content page.
I suggest we restructure this a little so that:
http://avalon.apache.org/api <--- framework api
http://avalon.apache.org/phoenix/api <--- phoenix api
http://avalon.apache.org/logkit/api <--- logkit api
http://avalon.apache.org/<product>/api <--- <product> api
Etc.
A consildated javadoc of everything could reside under:
http://avalon.apache.org/all/api <--- consildated api
What do you think.
- we link to http://nagoya.apache.org/gump/javadoc for the rest of the javadocs (after gump is fixed so that it actual generates our javadoc)
I think it is on Nicola's TODO, but he seems busy :D
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
