You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2021/12/07 08:35:00 UTC

[jira] [Updated] (LUCENE-10294) Avoid compiling javadocs twice in 'gradlew check'?

     [ https://issues.apache.org/jira/browse/LUCENE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Weiss updated LUCENE-10294:
---------------------------------
    Attachment: LUCENE-10294.patch

> 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
>         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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org