[
https://issues.apache.org/jira/browse/LUCENE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097858#comment-17097858
]
Dawid Weiss commented on LUCENE-9321:
-------------------------------------
bq. Instead of gathering all javedocs into one place and checking relative
links, could we fix the linting script to make it work with per-project folder
? In the script, I think we also can forbid someone to add relative links
(which strengthens interdependencies between sub-projects) any more.
I agree with Tomoko here. An additional bonus of not having cross-project
relative links is that javadocs displayed by IDEs work properly. The top-level
index is a different matter because it is for site needs only (and then you can
link relative javadocs for each package).
> 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: Tomoko Uchida
> Priority: Major
> Time Spent: 1h 20m
> 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
