In short, I agree with the orginial poster. I've caught myself looking at the online javadoc more than once and hoping that the 1.1-dev docs aren't too far from the 1.0 release version I'm using.
Hmm ... I may be biased (being a Struts developer), but I would think the
current approach makes more sense -- the *stable* docs are the ones in a
release, and the web site can talk about "what's new and cool".
I suppose that depends on what sort of developer you envision using the online docs. As a developer who USES the stable struts code in my own applications, I'd like to see the "stable" 1.0 docs online at the official source. When I need to look up a struts function, I turn to http://jakarta.apache.org/struts/api/ . For some reason, I've never liked deploying javadoc locally for "utility" jarfiles. It doesn't really make sense to consult remote javadoc , but all my javadoc bookmarks are like that. *shrug*
As a developer who's WORKING ON the struts code, I'd naturally think to look at my own (local) javadoc to keep track of (and update) the javadoc, right next to the (local) javadoc for the application I'm developing..
-tak
