sts-springsourcetoolsuite

I've downloaded and installed STS 3.8.2 on my Mac (10.12.1). Each time the STS.app file is launched, it creates a new org.springsource.sts_3.8.2.RELEASE_########_macosx_cocoa_x86_64 folder under the hidden .eclipse folder (the hashes are there because I have MANY of the same folder with the numbers in the hash area being the only difference). In doing so, the default workspace and all plugins I installed the last time it was running are wiped out (because they exist in the previous #### folder). I've tried installing the previous 3.8.1 and 3.8.0 version, but they are doing the same thing. My

When I run web app on server in STS internal web browser opens. I want to disable this but I don't know where can I do this. zb226 Eldelshell already sort of answered this, but I think a little more info might help other people. He's correct about going to Window -> Preferences -> General -> Web Browser and creating a new external external browser configuration. This will only work with an executable, though. Thus, entering /dev/null in the "Location" field won't work. What to put there depends on which type of operating system you're on, but basically you want to specifiy a command that doesn

I've been running STS 2.3.2 on a MacBook Pro for a few days now. I'm finding the performance to be significantly slower than any other build of Eclipse I've used. For example, switching from one tab to another can take up to 4 seconds. I tried turning off much of the validation, and increasing the memory, but it's not making a difference. Are others having similar experiences? I had the same problem on a MacBook Pro i7. Switching editors or views was painfully slow. Solved it by turning off Spring validators that I didn't need. Go to: SpringSource Tool Suite -> Preferences -> Spring -> Project

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

I am starting to configure my development environment and I am using Spring Tool Suite 2.8.1 along with m2E 1.01. As far as I can tell, since this is a Maven Project (my first), my Maven POM is dictating (along with m2E smarts) my project build configuration and dependencies. What I would like to know is why my IDE is displaying Java Build Problems that read "Archive required for library library/path/somejar.jar cannot be read or is not a valid zip file" when I can see the jars in my .m2 repository? All the errors pertained to commons-logging:1.1.1 which I excluded in my parent-pom. This was a

This question already has an answer here: Deploying Maven project throws java.util.zip.ZipException: invalid LOC header (bad signature) 17 answers When I run a Spring MVC application I get this exception and the sever fails to start. Please help me to fix this issue. Exception StackTrace: Jan 24, 2013 11:33:59 AM org.apache.catalina.startup.ContextConfig processAnnotationsJar SEVERE: Unable to process Jar entry [org/springframework/instrument/classloading/oc4j/package-info.class] from Jar [jar:file:/D:/works/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/dailyship/WEB-INF/lib

From now to then, my Maven 2 started to mess around. I am using SPring STS 2.6.1 and have a single project based on Spring 3, Hibernate, DWR, Cometd and all that stuff. Today I just updated from Git und all of a sudden, I got that scary mvn exclamation mark (!) next to my project. After hitting "Project -> Maven -> Update dependencies" I just receive: 24.05.11 15:26:58 MESZ: Missing artifact org.jdom:jdom:jar:1.1:compile 24.05.11 15:26:58 MESZ: Missing artifact org.apache.solr:solr-common:jar:1.3.0:compile 24.05.11 15:26:58 MESZ: Missing artifact org.apache.solr:solr-core:jar:1.3.0:compile 24