[
https://issues.apache.org/jira/browse/LUCENE-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521850#comment-17521850
]
Dawid Weiss commented on LUCENE-10510:
--------------------------------------
I suspected it might have been the nightly runs. We could try to detect whether
the JVM would run with an unexported jdk package (anything up until jdk16?) but
I think it buries the problem rather than solves it. I think it's easy to run a
first pass that generates those required JVM settings. If you for some reason
can't do it, pass them via command-line (or environment variables) directly to
gradle -
https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_environment_variables
this will also work, even in the absence of gradle.properties, as the task
verifies whether the required modules are open (not how or where they were
opened). Sorry for the complications - not my fault. :)
> 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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
