[
https://issues.apache.org/jira/browse/OAK-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777184#comment-17777184
]
Konrad Windszus edited comment on OAK-10500 at 10/19/23 10:57 AM:
------------------------------------------------------------------
No need to modify the pom. One can use the approach outlined in
https://stackoverflow.com/a/32980111/5155923 to exclude certain modules.
Probably it would be good idea to add the command line used to generate the
aggregate javadoc somewhere in the documentation.
Alternatively we can configure the skipped modules for javadoc only via
https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#skippedModules.
was (Author: kwin):
No need to modify the pom. One can use the approach outlined in
https://stackoverflow.com/a/32980111/5155923 to exclude certain modules.
Probably it would be good idea to add the command line used to generate the
aggregate javadoc somewhere in the documentation.
Alternatively we can configure the skipped modules for javadoc via
https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#skippedModules.
> javadoc:aggregate build fails again
> -----------------------------------
>
> Key: OAK-10500
> URL: https://issues.apache.org/jira/browse/OAK-10500
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: doc
> Reporter: Julian Reschke
> Priority: Minor
>
> For the public site, we're creating aggregate Javadocs for the whole project.
> This fails since the switch to Java 11, and is caused by the project pulling
> in different versions of lucene-core, which are not compatible (oak-update
> uses a historic one from Jackrabbit, oak-solr one a newer one than the
> defaulr project).
> In addition, doc generation for the groovy classes fails when shaded Guava is
> in the reactor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
