[ 
https://issues.apache.org/jira/browse/LUCENE-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044439#comment-17044439
 ] 

Robert Muir commented on LUCENE-9201:
-------------------------------------

as a second step you can look at computing package list for a module yourself 
(it may allow invoking the tool directly).

This way javadocs of {{lucene-demo}} don't have to depend on all the source 
code of all dependencies (such as lucene-core). 

We don't need to rebuild {{lucene-demo}} javadocs if there is a one-line change 
to {{lucene-core}}: instead only if a new package is introduced to it (this 
will alter generated hyperlinks)

> 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
>
>          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

Reply via email to