[
https://issues.apache.org/jira/browse/LUCENE-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521323#comment-17521323
]
Dawid Weiss commented on LUCENE-10510:
--------------------------------------
Hi Alan. The task graph is fine. When you run 'gradlew clean test' the new task
would not be included. If you take a look at the dependencies, it is only
included if either spotless is actually part of the execution graph or you run
java compilation with -Ptests.slow=true (in which case it is needed because
error-prone does require those vm opening settings). I think everything is set
up correctly. I believe your CI jobs were passing on 9x with JDKs older than 17
because those JDKs emitted a warning about package accesses. The right way to
fix the problem would be to add the right exports or, even better, run gradlew
help or an explicit gradlew localSettings to make sure everything is set up
correctly in gradle.properties.
> 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
