[
https://issues.apache.org/jira/browse/LUCENE-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033658#comment-17033658
]
Dawid Weiss commented on LUCENE-9201:
-------------------------------------
Gradle's built-in javadoc task is indeed pretty dumb with respect to the set of
options allowed by the javadoc tool. Maybe they take the lowest denominator
across all javadoc/jvm versions, I don't know.
We can change it, I don't mind. We don't even have to rely on ant - we can just
run javadoc as an external tool and build the set of options required.
The pull request attached to the issue has some odd fragments in it (filtering
for projects based on directory structure for example). I'm not familiar with
what ant does here. Should I review the PR or should we rather focus on trying
to remove python from the loop and use the built-in html validation combined
with custom doclet instead?
> Port documentation-lint task to Gradle build
> --------------------------------------------
>
> Key: LUCENE-9201
> URL: https://issues.apache.org/jira/browse/LUCENE-9201
> Project: Lucene - Core
> Issue Type: Sub-task
> Affects Versions: master (9.0)
> Reporter: Tomoko Uchida
> Assignee: Tomoko Uchida
> Priority: Major
> Attachments: javadocGRADLE.png, javadocHTML4.png, javadocHTML5.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ant build's "documentation-lint" target consists of those two sub targets.
> * "-ecj-javadoc-lint" (Javadoc linting by ECJ)
> * "-documentation-lint"(Missing javadocs / broken links check by python
> scripts)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
