[
https://issues.apache.org/jira/browse/LUCENE-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081747#comment-17081747
]
Dawid Weiss commented on LUCENE-9201:
-------------------------------------
On the second thought I think we should keep the convention 'javadoc' task call
'renderJavadoc' so that people can still invoke ':foo:bar:javadoc' and it'll
work. I'll do this change. Make all other task depend on renderJavadoc though
(not javadoc). The difference is that gradle's javadoc first compiles stuff (we
don't have to do that in renderJavadoc).
> 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: LUCENE-9201-ecj-2.patch, LUCENE-9201-ecj.patch,
> LUCENE-9201-missing-docs.patch, LUCENE-9201.patch, javadocGRADLE.png,
> javadocHTML4.png, javadocHTML5.png, task_deps1.png, task_deps2.png
>
> Time Spent: 4.5h
> 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
