[
https://issues.apache.org/jira/browse/MJAVADOC-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957849#comment-17957849
]
Olivier Lamy commented on MJAVADOC-492:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#786|https://github.com/apache/maven-javadoc-plugin/issues/786].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Need a way to aggregate subproject javadocs without regenerating them
> ---------------------------------------------------------------------
>
> Key: MJAVADOC-492
> URL: https://issues.apache.org/jira/browse/MJAVADOC-492
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.10.4
> Reporter: David M. Karr
> Priority: Major
>
> I work on a largish multiproject build. I implemented a custom javadoc
> taglet that will be used in each project (although only in one so far). This
> taglet needs to access the class file associated with the source file the tag
> is contained within. I've gotten this to work in each project by overriding
> the "tagletArtifacts" list in each subproject (with
> combine.children="append"), adding the GAV for the artifact produced by that
> POM. The main configuration for maven-javadoc-plugin is defined in the parent
> pom that all the subprojects have as their parent pom.
> However, the javadoc output in each subproject is really just a validation
> step, because the deliverable I need is the aggregation of the javadoc of all
> of the subprojects, which I generate from the root project with
> "javadoc:aggregate-jar". This doesn't aggregate the already created output
> from each subproject, it really just regenerates it all again.
> Unfortunately, this does not use the overridden "tagletArtifacts" list in
> each subproject, so when the taglet runs, it can't find the class file and
> fails to generate its output.
> The only "fix" I can see for this at this time is to go into the parent pom,
> editing the configuration for the execution element for "aggregate-jar",
> adding a tagletArtifacts list that incliudes the GAVs for all of the
> subprojects, the exact kind of thing I was trying to avoid doing by using the
> 'combine.children="append"' approach in each subproject.
> I've looked at the documentation for the maven-javadoc-plugin, and I don't
> see any other way around this. What I really need is a way to somehow
> "merge" the already generated javadoc output for each subproject, or somehow
> allow the "aggregate-jar" goal in the root project get information out of
> each subproject for the tagletArtifacts list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
