[
https://issues.apache.org/jira/browse/TIKA-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890037#comment-17890037
]
Tim Allison commented on TIKA-4318:
-----------------------------------
My initial memory on this issue was that the autogenerated classes in grpc were
causing problems. I then stubbed my toes for a while trying to get everything
working and couldn't find any problems with grpc... until I went to make the
release. During the final step in {{release:perform}}, javadoc errors out on
grpc with the autogenerated classes.
I turned back on the "ignore javadocs" for grpc in 3.x.
Once we make the release, we can maybe move the autogenerated classes to their
own package in 4.x and then configure javadoc to ignore that package.
If anyone has any better ideas, please share. This was not a great way to spend
time.
> 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.0.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)
