[
https://issues.apache.org/jira/browse/SOLR-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070035#comment-18070035
]
Dawid Weiss commented on SOLR-18184:
------------------------------------
If I recall right, it was difficult to pick an explicit jvm with toolschains (a
custom jdk, for example). Even with precedence rules [1], it wasn't possible to
just say: use this jvm, from this location. I don't think this is as relevant
for Solr.
[1] https://docs.gradle.org/current/userguide/toolchains.html#sec:precedence
> Gradle: use "toolchains" to select the Java VM
> ----------------------------------------------
>
> Key: SOLR-18184
> URL: https://issues.apache.org/jira/browse/SOLR-18184
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: David Smiley
> Priority: Major
> Attachments: idempotent-wandering-micali.md
>
>
> This issue proposed switching our Gradle build's JVM selection to use Gradle
> Toolchain. This is convenient for users, as they might have JDK 17 when they
> invoke Gradle, and need not switch to JDK 21 just because Solr requires JDK
> 21 to build. It's also more expected/standard.... it appears that our build
> had expressly avoided this "obvious" choice IMO.
> Indeed that's the case in Lucene land – toolchains were avoided, at least
> because of some issues with selecting preview/EA releases. That doesn't seem
> relevant to us.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
