[
https://issues.apache.org/jira/browse/TIKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866742#comment-17866742
]
Tim Allison commented on TIKA-4281:
-----------------------------------
Well, that didn't work: {{javadoc: error - No source files for package ...}}.
This is likely the problem that lead to adding the sourcepath.
What I can't figure out is that {{javadocs:aggregate}} ran without any
complaints even in debug mode (that I could find in the voluminous logs) but
left nothing {{target/site}}. When I removed the <sourcepath/> line in the
3.0.0-BETA2 release's pom, {{javadocs:aggregate}} worked as expected. However,
now we're getting that javadoc error in ci/cd, and I'm getting a related one --
just a different package -- locally.
> Fix javadoc plugin configuration
> --------------------------------
>
> Key: TIKA-4281
> URL: https://issues.apache.org/jira/browse/TIKA-4281
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
>
> We added <sourcepath>src/main/java</sourcepath> to our parent pom back in
> April when we updated the Apache parent pom. This line prevented the
> generation of javadocs for the 3.0.0-BETA2 release. I don't know if we need
> that line with our current version of the ASF parent pom.
> Let's figure it out.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
