[
https://issues.jboss.org/browse/AS7-582?page=com.atlassian.jira.plugin.sy...
]
John Casey reassigned AS7-582:
------------------------------
Assignee: Shelly McGowan (was: John Casey)
I can't move on this until we have more information about how public/private sources
are to be marked, and at what actual scope.
Once we have specific information on that, we can create a java annotation processor that
will generate a list of files to be processed by the javadoc tool, based on some
annotation or other marker.
I can help with this once we have more information, but I'm not plugged into the
deadline discussions for this work, so I'm mostly unaware of timeframes being
discussed for having this tooling done.
Feel free to re-assign back to me when we have more information.
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: Shelly McGowan
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