[jboss-jira] [JBoss JIRA] Updated: (JBAS-9026) Create JBoss AS Javadoc aggregate project

[David Lloyd (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd updated JBAS-9026:
------------------------------

    Description: 
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.

  was:
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.



> Create JBoss AS Javadoc aggregate project
> -----------------------------------------
>
>                 Key: JBAS-9026
>                 URL: https://issues.jboss.org/browse/JBAS-9026
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>            Assignee: John Casey
>             Fix For: 7.0.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira