On Tue, 15 Mar 2005, Martin Cooper wrote:
On Wed, 16 Mar 2005 00:49:08 -0500 (EST), Henri Yandell <[EMAIL PROTECTED]> wrote:
Interested in finding out if anyone else thinks this would be a good idea.
Rather than have each subproject managing their release javadocs separately, I think it would be good if we treated the javadoc more like the releases. Located in a central location, perhaps mirrored, all versions available and perhaps with additional tools like ashkelon or multidoc to bring them together.
Sounds good to me (assuming you mean all *released* versions available). On download pages, we could have binaries, sources and javadocs, with options for javadocs being download or view online (a bit like Sun's download pages). We might not need to mirror right away - we could wait to see how much this gets used.
Yep. Unsure if the download page would be the best place for the view online option though.
I'm not familiar with ashkelon or multidoc. What would they bring to the party?
Ashkelon is an alternative to javadoc really. You load the javadoc into a database and it gives you a searchable system and a slightly more descriptive version of javadoc. I've a basic version running at:
http://issues.osjava.org/ashkelon/apis.do
while http://www.jdocs.com/ have a more customised version. It requires a db and a tomcat server.
Multidocs is a hack of mine. It scrapes from various existing javadoc urls and builds a wrapper around them:
http://www.apache.org/~bayard/multidoc/commons-multidoc/
I also had it doing src xref, test coverage etc.
Low cost, but all it really adds is a nicer way for the user to find the javadoc they want.
Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
