[ http://jira.codehaus.org/browse/MJAVADOC-33?page=all ]
Brett Porter closed MJAVADOC-33:
--------------------------------
Resolution: Fixed
> Provide new javadoc:aggregate goal to perform javadoc operation on project
> and subprojects.
> -------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-33
> URL: http://jira.codehaus.org/browse/MJAVADOC-33
> Project: Maven 2.x Javadoc Plugin
> Type: Improvement
> Reporter: John Allen
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-4
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> Provide new javadoc:aggregate goal to perform javadoc operation on a project
> and its subprojects, idea being that aggregate pulls together the classpath
> and sourcepath for all the project and subprojects and then churns out normal
> javadoc.
> i.e. projects:-
> /root/
> /root/a/src/...
> /root/a/b/src/...
> /root/a/b/c/src/...
> /root/a/d/src/...
> /root/a/e/src/...
> @ /root/a-> m2 javadoc:aggregate
> generates javadoc in /root/a/target/javadoc for src contained within projects
> a, b, c, d, and e.
> Note, javadoc does not currently provide support for this kind of aggregation
> and so people have traditionally written their own specialised tasks/scripts
> (in ant land say) to handle it. sun do refer to the idea of an incremental
> build in their FAQ which they say they are considering for the future (fat
> chance) (http://java.sun.com/j2se/javadoc/faq/#incrementalbuild) but that is
> about generating aggregate docs from already existing javadocs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
