Just for my clarification. I know if you want to include javadocs in an
IDE, which I do, an easy method to download the javadocs should be
handled some way. I wasn't clear if that was the final outcome or not?
Currently I build derby javadocs, then zip them, or use it as a folder,
so the IDE can give me some hints. So it would be nice if you were
thinking about a method to distribute the docs (which I wasn't certain
if that was what Andrew was saying). I would guess a zip file would be
the easiest method to download them? Was this a portion of the outcome?
thanks,
scott
Laura Stewart wrote:
On 3/9/07, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
I'm not spotting a reference to the Apache javadoc site in the Getting
Started Guide. In any case, we shouldn't include a link to
http://db.apache.org/derby/javadoc/engine/ in documentation intended for
users.
If we include the link to the html for the API on the main doc page at
http://db.apache.org/derby/manuals/index.html
Why shouldn't we include a link in the Getting Started Guide to the
same html file?
The main doc page is for users, not just source code developers...
Or am I missing something here?
