There is a benefit to All Packages, as well as individual packages. And I
would be seriously happy (although I'm not planning to do anything in James
to do it, ourselves), if there were a link from the javadocs to the cvs
repository. :-)
Quick. Find: org.apache.log.output.io.rotate.OrRotateStrategy. Which
module do you look in, if you don't know that it is part of the
avalon-logkit module?
--- Noel
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 08, 2003 22:28
To: Avalon Developers List
Subject: Javadoc links in Avalon
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.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
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]
