#0 LONG PATH TOOL 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. 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.
#0 LONG PATH TOOL ZIP FILE#
But keep in mind that this problem happens only if you use the Windows built-in ZIP file support to unzip STS4.
#0 LONG PATH TOOL INSTALL#
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). I can commit and push fine using git bash just sourcetree keeps staging for delete.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). I also fully rebooted my machine cause well. I double checked and sourcetree is using the system git instead of the embedded git, I checked three times to be sure. Http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crtį=git-lfs filter-processĬore.excludesfile=C:\Users\MyUser\Documents\gitignore_global.txt This is my current git config core.symlinks=false I followed all the steps but the problem persists. Is this a bug in the current sourcetree or can this be fixed with a parameter ? This is a very dangerous development cause if a code reviewer misses this in one pull request the project code if not unit tested properly could get messed up. I can commit the file just fine with command line git or even in inteliJ. However when I try to stage a file longer then 260 chars sourcetree stages it for delete. I can checkout my project from bitbucket perfectly and work on it in inteliJ.
Http.sslcainfo=C:/Program notice the core.longpaths option there. I'm using windows 7 and sourcetree 1.9.10.0 with following in my git config file