[
https://issues.apache.org/jira/browse/LUCENE-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542778#comment-17542778
]
Dawid Weiss commented on LUCENE-10510:
--------------------------------------
This is caused by google formatter accessing JVM internals. The first tidy
failure tries to actually explain why it's failed - this is the message you
were getting:
{code}
* What went wrong:
Execution failed for task ':checkJdkInternalsExportedToGradle'.
> Certain gradle tasks and plugins require access to jdk.compiler internals,
> your gradle.properties might have just been generated or could be out of sync
> (see help/localSettings.txt)
{code}
I'm not sure what can be improved here but feel free to suggest something to
your liking!
> Check module access prior to running gjf/spotless/errorprone tasks
> ------------------------------------------------------------------
>
> Key: LUCENE-10510
> URL: https://issues.apache.org/jira/browse/LUCENE-10510
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 9.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> PR at: [https://github.com/apache/lucene/pull/802]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
