[ https://issues.apache.org/jira/browse/HARMONY-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892155#action_12892155 ] 

Chad Retz commented on HARMONY-6443:
------------------------------------

Just caught this issue. I am attempting a 100% apache licensed implementation of javadoc at http://code.google.com/p/javadoc-ng/. It's in its infancy and it uses QDox (also apache 2 licensed) to parse, but the parser and outputter are pluggable so they can use anything and output in any format. The initial goal is complete compatibility with the existing Sun javadoc generated pages

> [jdktools] Implement the javadoc command line tool
> --------------------------------------------------
>
>                 Key: HARMONY-6443
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6443
>             Project: Harmony
>          Issue Type: Task
>          Components: JDK
>            Reporter: Mark Hindess
>            Assignee: Oliver Deakin
>
> javadoc is the JDK tool for parsing javadoc comments to produce documentation.  See:
>   http://java.sun.com/javase/6/docs/technotes/guides/javadoc/index.html
> It is expected that it will be written in Java using the existing samsa framework in Harmony.  It will be necessary to implement the DocLet and TagLet APIs in order to complete this task.  The implementation should be compatible with the Sun tool but it could be extended with other features - such as richer HTML output with ajax, css, etc. - to add value to the Harmony implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.