[
https://issues.apache.org/jira/browse/TIKA-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889684#comment-17889684
]
Tim Allison edited comment on TIKA-4318 at 10/15/24 2:04 PM:
-------------------------------------------------------------
Removing {{<sourcepath>src/main/java</sourcepath>}} causes ci/cd to fail.
{noformat}
Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.10.1:aggregate (default-cli) on
project tika: An error has occurred in Javadoc report generation:
2024-10-15T13:41:51.8978543Z [ERROR] Exit code: 2
2024-10-15T13:41:51.8979146Z [ERROR] error: No source files for package
org.apache.tika.io
{noformat}
Locally, the build works with Java 11 and 17, but there are no javadocs output
in {{target/reports}} or anywhere in {{target}}.
was (Author: [email protected]):
Removing {{<sourcepath>src/main/java</sourcepath>}} causes ci/cd to fail.
Locally, the build works with Java 11 and 17, but there are no javadocs output
in {{target/reports}} or anywhere in {{target}}.
> 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}}. My memory is that there was a problem with the autogenerated
> code in grpc.
> 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)
