spring-tool-suite

Eclipse Organize Imports Shortcut (Ctrl+Shift+O) is not working

喜欢而已 提交于 2019-11-28 08:03:19
Eclipse used to import missing packages when I press Ctrl + Shift + O . The shortcut key has stopped working when used in Java files but the same shortcut is working in Python files (importing missing packages). Any thoughts on how to fix the issue. Below are couple of snapshots for your reference. user2153465 To fix this issue: Go to Preferences -> General -> Keys Click on Filters... and de-select Filter uncategorized commands then Ok . Then look for the command Go To Symbol in File and select it. Then click on Unbind and then Apply and Close Ctrl + Shift + O . should now work. EDIT: Also

Failed to start component - ZipException: invalid LOC header (bad signature) [duplicate]

倾然丶 夕夏残阳落幕 提交于 2019-11-27 17:45:04
问题 This question already has answers here : Deploying Maven project throws java.util.zip.ZipException: invalid LOC header (bad signature) (12 answers) Closed last year . I have gone through similar posts around. I have tried most of those solutions but was not able to get rid of the error I am getting. Expecting some help on this. This error came after I added maven dependancies to deployment assembly. I am using STS with Pivotal tc Server Development Edition v3.1. I already checked the version

Is it possible for Gradle projects in Eclipse/STS to resolve dependencies to other Gradle projects in the same workspace?

主宰稳场 提交于 2019-11-27 15:41:41
A Gradle project in my workspace (call it Downstream ) needs to depend on another Gradle project (call it Upstream ). Outside of Eclipse, of course Upstream would need to be build and install ed before Downstream (so that Gradle can resolve it). In Eclipse, since both projects are in the workspace together, I'd like to have Gradle look in the workspace first and make the dependency between the projects, not from the repo. m2e (Maven integration for Eclipse) does this (the option is called Resolve dependencies from Workspace ). Gradle Eclipse plugin has an option called Remap Jars to maven

Hiding Duplicate Toolbars Items in Eclipse

▼魔方 西西 提交于 2019-11-27 09:06:01
I don't know how, but my STS has got duplicate toolbars items and I am not sure how to remove them. Here is how my duplicated toolbar looks like. I want to get rid of these. I tried to hide the toolbar but that didn't help. Does anybody have any idea how to get rid of the duplicate ones? I've been having the same problem since upgrading to Oxygen. I haven't been able to reliably reproduce the issue. The workaround suggested by @howlger has helped and is less intrusive than blowing away the entire workspace: Close Eclipse. In the Eclipse workspace directory, delete the .metadata\.plugins\org

Hiding Duplicate Toolbars Items in Eclipse

天涯浪子 提交于 2019-11-26 17:48:10
问题 I don't know how, but my STS has got duplicate toolbars items and I am not sure how to remove them. Here is how my duplicated toolbar looks like. I want to get rid of these. I tried to hide the toolbar but that didn't help. Does anybody have any idea how to get rid of the duplicate ones? 回答1: I've been having the same problem since upgrading to Oxygen. I haven't been able to reliably reproduce the issue. The workaround suggested by @howlger has helped and is less intrusive than blowing away

Is it possible for Gradle projects in Eclipse/STS to resolve dependencies to other Gradle projects in the same workspace?

旧城冷巷雨未停 提交于 2019-11-26 17:18:34
问题 A Gradle project in my workspace (call it Downstream ) needs to depend on another Gradle project (call it Upstream ). Outside of Eclipse, of course Upstream would need to be build and install ed before Downstream (so that Gradle can resolve it). In Eclipse, since both projects are in the workspace together, I'd like to have Gradle look in the workspace first and make the dependency between the projects, not from the repo. m2e (Maven integration for Eclipse) does this (the option is called