Installing old runtime versions may render your IDE unusable or introduce new issues. It makes sense to install the most recent version or the version you were asked to try by JetBrains staff. Select the version to install, the higher the number after b, the more recent is the version.Start the IDE, use Help | Find Action (Ctrl+Shift+A or Cmd+Shift+A on Mac), type " Choose Boot Java Runtime for the IDE", press Enter.All platforms: download and install JetBrains Runtime via Choose Boot Java Runtime for the IDE action Our IDEs will not run on the older Java versions like Java 8 or 11.
Please note that all the current IDE versions require at least Java 17 version to run. If you need to change the runtime to a different version, see below. If it has been configured differently, this must of course be adjusted accordingly.Įdit: the range around "192.168.0.0/16" should also be entered, as this is also used by WSL2.All the products on all the supported platforms already have 64-bit JetBrains Runtime 17 bundled and it will be used by default to run the IDE. The IP is entered under "Range" and "Remote IP address".īy default, the WSL2 is assigned an IP address that comes from this range. The values can be made via a right click on the corresponding entry and properties. For the entry for Public and TCP the action must be set to "Allow", but only for the remote address "172.16.0.0/12".Search for "Windows Defender Firewall with Advanced Security" in Windows Search and search for " VcXsrv windows server" under " Incoming rules".Windows Defender blocks access from WSL to the X11 server by default: Īccess can be allowed via firewall rules: The file can also be placed in the autostart, then the X11 server starts already preconfigured at login. This can look as follows (can be saved as " config.xlaunch" for example): VcXsrv is then started by means of a config file. This can be downloaded here for example: This requires the following steps:įirst of all, the X11 server must be installed. This can be worked around by installing PHPStorm directly into WSL2 and using an X11 server to display the windows in Windows. In PHPStorm the project can then be called via the path \\wsl$\Ubuntu\home\\.\. Quickly it becomes clear that PHPStorm does not reliably recognize changes to the files. As a workaround you can move the projects to the file system of WSL2, for example to /home//./. The project itself can be located under /mnt/ (directly accessible via Windows Explorer), but then the performance is quite bad. PHPStorm can of course also be installed normally, as you know it from Windows programs:
0 kommentar(er)
