[jira] Closed: (MJAVADOC-280) Allow creation of aggregated javadocs source bundles from project dependencies

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MJAVADOC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MJAVADOC-280.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.6.2)
                   2.7

Fixed, tested, documented.

> Allow creation of aggregated javadocs source bundles from project dependencies
> ------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-280
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-280
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.6.1
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.7
>
>         Attachments: aggregate-from-dependencies.patch
>
>
> It would be nice to have the ability to generate an aggregated javadoc set for a distribution project by resolving the -sources and -test-sources bundles of its dependencies (or, correspondingly, the project.compileSourceRoots and project.testCompileSourceRoots for modules in the same reactor).
> Initially, this might just mean downloading, unpacking, and adding the dependency sources as sourcepaths to the javadoc execution if a flag is set to true (includeDependencySources). Later, we could easily expand this to allow bundling and deployment of the src/main/javadoc directory so that this artifact can be used in the above aggregation approach.
> I've got an implementation of the first part that I will attach to this issue as a patch to illustrate what I'm talking about.

-- 
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