It looks like the new version of CLion expects either JRE_HOME or JDK_HOME to point to a valid Java install. The other JetBrains IDEs don't care about those environment variables. OpenJDK 17 is defined as a runtime dependency for CLion and therefore already installed by default.
Should we consider this OUR problem and let either of the envvars point to /user/lib/openjdk-17 - or should we consider this a USER problem and just let them run into the error message and figure it out by themselves?
It looks like the new version of CLion expects either JRE_HOME or JDK_HOME to point to a valid Java install. The other JetBrains IDEs don't care about those environment variables. OpenJDK 17 is defined as a runtime dependency for CLion and therefore already installed by default.
Should we consider this OUR problem and let either of the envvars point to
/user/lib/openjdk-17
- or should we consider this a USER problem and just let them run into the error message and figure it out by themselves?