Issue 30: Need to add basic javadoc comments to code
Project Member Reported by kandpwel...@gmail.com, Dec 5, 2011
I'm sure we (I) need to do the full 9 yards. But to start I thought I should at least get basic docs for the public API. That way we can start playing with the build to get javadoc created and stored and accessible in docs.  I have lots of questions arounds javadocs, versioning, linking to external docs, repackaged external dependencies, styling, and much more. 
Dec 6, 2011
Project Member #1 codeto...@gmail.com
+1 for the public API, certainly. I don't know about the full 9 yards. I'd prefer tests and clear code over doc. 
Dec 7, 2011
Project Member #2 kandpwel...@gmail.com
adding label
Labels: Component-Docs
Dec 12, 2011
Project Member #3 kandpwel...@gmail.com
adding priority
Labels: Priority-Critical
Dec 16, 2011
Project Member #4 kandpwel...@gmail.com
adding milestone
Labels: Milestone-Release0.1
Dec 27, 2011
Project Member #5 kandpwel...@gmail.com
I would like to be able to link to external Javadoc for external classes (Guava, Functional Java, Jedi, and maybe Java 1.5).  It looks like one enables this with the "-link" javadoc option.  I'm not sure how to add this to our gradle build.  If you (codetojoy) do not take this task, I will look into it when I get a chance.
Status: Started
Jan 4, 2012
Project Member #6 kandpwel...@gmail.com
copied my last comment into a new issue, and closing this issue.  Docs could be better and more expansive, but they are a sufficient start for the public classes.
Status: Fixed