[MJAVADOC-280] Allow creation of aggregated javadocs source bundles from project dependencies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.1
• Fix Version/s: 2.7
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 07/Apr/10 15:58
• Updated: 05/Apr/15 14:44
• Resolved: 12/Apr/10 16:26

Description

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.

Issue Links

• duplicates: MJAVADOC-265 Generate a combined javadoc using all dependency source jars.
• is related to: MJAVADOC-340 Javadoc generation with includeDependencySources=true crashes when any of those dependencies have scope=provided dependencies
• relates to: MJAVADOC-320 includeDependencySources does not handle external dependencies and filters for reactor dependencies correctly
• relates to: MJAVADOC-339 useStrictFiltering support in javadoc plugin for dependencySourceIncludes and dependencySourceExcludes