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

Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2026/03/31 15:34:00 UTC

[jira] [Commented] (SOLR-18184) Gradle: use "toolchains" to select the Java VM

    [ https://issues.apache.org/jira/browse/SOLR-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069968#comment-18069968 ] 

David Smiley commented on SOLR-18184:
-------------------------------------

The attached plan was developed by me & Claude.  It calls for removing our bespoke RUNTIME_JAVA_HOME thing.

Concerns?  CC [~dweiss] [~uschindler] [~malliaridis] 

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