Because of this issue I am wondering if there is a way to set up a different JDK when running the runIde task?
I looked in here but couldn’t find a proper section on how to do it.
Because of this issue I am wondering if there is a way to set up a different JDK when running the runIde task?
I looked in here but couldn’t find a proper section on how to do it.
I think it actually is mentioned in the doc you linked:
To resolve the
jbr_jcef-21.0.3-osx-aarch64-b446.1.tar.gz
archive, you can use:
jetbrainsRuntime("21.0.3b446.1", "osx", "aarch64")
jetbrainsRuntime("21.0.3b446.1")
(os
andarchitecture
are by default resolved with the current environment)jetbrainsRuntimeExplicit("jbr_jcef-21.0.3-osx-aarch64-b446.1")
But I can’t use Jbr - the workaround suggested in the YouTrack is to use Amazon corretto
@yann.cebron , @jakub.chrzanowski any chance you can help me better understand JetBrains position about the issue above (youtrack)?
This is a huge stopper for me and in the ticket they are talking about 2025.2.
Not sure how it is even possible since from my understanding it will affect a huge number of JetBrains’ users once Apple will release the beta version.