[
https://jira.codehaus.org/browse/MJAVADOC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288531#comment-288531
]
Geoffrey De Smet commented on MJAVADOC-280:
-------------------------------------------
Please reopen this issue: it doesn't work in 2.8.
With this configuration it still only generates the javadocs of the current
module in target/apidocs
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
<configuration>
<includeDependencySources>true</includeDependencySources>
<dependencySourceIncludes>
<dependencySourceInclude>org.drools:*</dependencySourceInclude>
</dependencySourceIncludes>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<!-- Internal dependencies -->
<dependency>
<groupId>org.drools</groupId>
<artifactId>knowledge-api</artifactId>
</dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>knowledge-api</artifactId>
<classifier>sources</classifier>
</dependency>
...
{code}
Here's someone else having the same problem.
http://maven.40175.n5.nabble.com/Aggregating-Javadocs-from-Dependency-Sources-td126034.html
> Allow creation of aggregated javadocs source bundles from project dependencies
> ------------------------------------------------------------------------------
>
> Key: MJAVADOC-280
> URL: https://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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
