[
https://issues.apache.org/jira/browse/LUCENE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101589#comment-17101589
]
Tomoko Uchida commented on LUCENE-9321:
---------------------------------------
I'm not certain if it affects discussion here though, there's a thing that is
not very clear to me. (Sorry if I missed something.)
Once "documentation" task is done, I plan to work on "checkBrokenLink" task
(equivalent of Ant's "check-broken-links" macro). For the purpose of the task,
it will depend on "documentation" (since it checks the javadocs w/ relative
paths generated by "documentation").
My question is: when the "checkBrokenLink" should be invoked ? If we want to
include it in "precommit", "documentation" will also be (cascadingly) called
when people call precommit every time. If it is not preferred, we'd need to
consider where the check belong to (only Jenkins and release manager care of
it?).
> Port documentation task to gradle
> ---------------------------------
>
> Key: LUCENE-9321
> URL: https://issues.apache.org/jira/browse/LUCENE-9321
> Project: Lucene - Core
> Issue Type: Sub-task
> Components: general/build
> Reporter: Tomoko Uchida
> Assignee: Uwe Schindler
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: screenshot-1.png
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> This is a placeholder issue for porting ant "documentation" task to gradle.
> The generated documents should be able to be published on lucene.apache.org
> web site on "as-is" basis.
--
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
