raises a warning “External file changes sync may be slow” From what I gathered it’s because WebStorm can’t start the fsnotifier64 on a network drive, which it thinks our Linux is on. This however causes a number of problems listed below This problem has been described well by a lot of blog posts and bug reports, and everyone suggests to keep your project files on native Linux filesystem, for example /home//projects like I do. Here’s a list of the problems I myself encountered when using WebStorm with WSL2 (the problems are the same in any of their tools - WebStorm, P圜harm and IntelliJ): Example problems If you try it, please let us know how it goes.If you managed to get here then I’m assuming you also have problems using Jetbrains tools with Windows Subsystem for Linux 2 (WSL2). It should unpack a copy of STS right next to the self-extracting jar.
#Long path tool intellij install
Copy the file to where you want to install STS and then double click it. There find the file that ends in win32.x86_64.self-extracting.jar.
![long path tool intellij long path tool intellij](https://1.bp.blogspot.com/-koSIOxO8f4c/X9YpYgBZwUI/AAAAAAAAGrE/GZPHK5DP5Cc-wMydrZ3USO2a_RVr_3q-ACLcBGAsYHQ/s1862/IntelliJ%2BProxy%2BSettings.png)
![long path tool intellij long path tool intellij](https://i.stack.imgur.com/Pl7WD.png)
Scroll down to the section SPRING TOOL SUITE 4 - BASED ON ECLIPSE 2019-09 RELEASE (4.13.0). unpacks itself without showing any error popups). I wonder if you want to try it out and let us know if the self-extracting jar works better (i.e.
#Long path tool intellij archive
Actually, we already have a self extracting archive available for nightly builds though it is not yet being published on the official/main STS download page for STS 4 release. We are working on a self-extracting jar archive specially to address this issue for Windows users. The error is worrying since, although you may not notice this readily, missing classes will cause unpredictable / broken behavior (essentially some part of STS implementation is effectively missing from the installation). We were assuming that the problem would allways be avoided by using 7zip. But there are good and easy-to-use solutions available if you come across this issue - as Interesting that you still have a 'path too long' error with 7zip.
![long path tool intellij long path tool intellij](https://imgs.developpaper.com/imgs/3330307049-5d9e9b4553361_articlex.jpg)
So yes, I think editing the registry is not the best option and the others should probably have been mentioned earlier here. Something that every Java dev should have installed and ready-to-use. In addition to that you can even use the jar tool of the JDK to unzip the STS4 distribution on your windows system via the command line: jar xf spring-tool-suite-4-4.3.0.RELEASE-e4.12.86_64.zip. It works just fine (and a lot faster) if you use one of the many ZIP tools for Windows that are out there (for example 7-Zip), which I would recommend independent of this issue when you deal with ZIP files on Windows.
#Long path tool intellij zip file
But keep in mind that this problem happens only if you use the Windows built-in ZIP file support to unzip STS4. Having long or deeply nested package names makes it more likely to hit this issue, long bundle names in Eclipse installs can cause the same (even though less likely than exploded JARs with deeply nested package structures).Įditing the windows registry to enable support for long path is indeed a bit crude in order to be able to install STS4, I totally agree (I wonder why that support isn't enabled in Windows by default though, but that is another story). First of all, the "path too long" problem is a long-standing and well-known issue on the windows operating system, especially when you unzip Java applications (but not alone Java apps).