[
https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456247#comment-17456247
]
ASF subversion and git services commented on LUCENE-10294:
----------------------------------------------------------
Commit 17aaab654e8eca4489daed525d6a9eef432746e6 in lucene's branch
refs/heads/branch_9x from Dawid Weiss
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=17aaab6 ]
LUCENE-10294: Avoid compiling javadocs twice in 'gradlew check'.
> Avoid compiling javadocs twice in 'gradlew check'?
> --------------------------------------------------
>
> Key: LUCENE-10294
> URL: https://issues.apache.org/jira/browse/LUCENE-10294
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 9.1
>
> Attachments: LUCENE-10294.patch
>
>
> Currently javadocs are rendered for the purposes of the local documentation
> (maven artifacts) and for the site (with cross-links). As many of you perhaps
> have observed, the time to render javadocs is quite significant. I've been
> wondering whether we can limit the top-level 'check' to just rendering
> javadocs once - just the site ones. This still runs the same linter checks,
> etc. so no harm is done and it speeds up the overall process.
> The downside is that a project-local 'check' wouldn't run javadoc linting. So
> 'gradlew -p lucene/core check' wouldn't run javadoc.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
