[
https://issues.apache.org/jira/browse/TIKA-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955020#comment-17955020
]
Tim Allison commented on TIKA-4318:
-----------------------------------
The workaround for 3.2.0:
1) take the grpc module off the pom (until we fix this: cannot access
com.google.errorprone.annotations.CheckReturnValue
> > > class file for com.google.errorprone.annotations.CheckReturnValue)
2) configure the javadoc plugin like so:
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>${maven.javadoc.version}</version>
<configuration>
<doclint>none</doclint>
</configuration>
</plugin>
{noformat}
3. run {{mvn clean javadoc:aggregate}}
I could get past the initial grpc problem by calling {{mvn clean package}} and
then javadoc:aggregate, but that builds jars, which (I'm guessing) starts
putting our automatic namespaces into play, and those aren't great, apparently,
with the plugin.
See the link via [~ndipiazza]:
https://issues.apache.org/jira/browse/MJAVADOC-764
> Fix javadoc aggregate in 3.x
> ----------------------------
>
> Key: TIKA-4318
> URL: https://issues.apache.org/jira/browse/TIKA-4318
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Minor
> Fix For: 3.1.0
>
>
> When I ran the 3.0.0-BETA2 release, I ran into problems with {{javadoc
> aggregate}}.
> Let's see if we can get this to work for the 3.0.0 release?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
