[jboss-jira] [JBoss JIRA] (AS7-582) Create JBoss AS Javadoc aggregate project

[Paul Gier (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649012#comment-12649012 ] 

Paul Gier commented on AS7-582:
-------------------------------

John, you are right, this should just be a single combined jar created in the build module.
I did some testing myself, but I ran into [MJAVADOC-320|http://jira.codehaus.org/browse/MJAVADOC-320] which is already fixed upstream.  The 2.8.1-SNAPSHOT version of the plugin seems to work ok, and I created a simple prototype which only includes the servlet and ejb apis in github.  We might need to do a release of the javadoc plugin before we get this working properly.
https://github.com/pgier/jboss-as/tree/AS7-582
                
> Create JBoss AS Javadoc aggregate project
> -----------------------------------------
>
>                 Key: AS7-582
>                 URL: https://issues.jboss.org/browse/AS7-582
>             Project: Application Server 7
>          Issue Type: Sub-task
>            Reporter: David Lloyd
>            Assignee: Vladimir Dosoudil
>             Fix For: 7.1.0.CR1
>
>
> Identify artifacts corresponding to "supported" API modules.  Generate aggregated JavaDoc by fetching the source JAR for each API artifact.
> Enable APIViz if possible; use JBoss.org theme if possible.
> Javadoc'd packages should be grouped by API.
> It is also important that JDK classes are properly linked.  This might mean linking to oracle's doc site for JavaSE like many projects do, or perhaps using locally-generated javadoc from OpenJDK perhaps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira