spring-tool-suite

I have faced following weird exception on GGTS IDE . Command terminated with an exception: org.grails.ide.eclipse.longrunning.client.GrailsProcessDiedException: Grails process died (see details for partial output) Grails process died ------System.out:----------- ------System.err:----------- I tried with following releases and still got same issue groovy-grails-tool-suite-3.3.0.RELEASE-e3.8.2-macosx-cocoa-x86_64-installer.dmg groovy-grails-tool-suite-3.3.0.RELEASE-e4.3-macosx-cocoa-x86_64-installer.dmg Operation System is MAC OS X Version 10.7.5 JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1

I use STS(spring tool suite) + maven plugin. Every time when I run my application using maven-clean I see following error: [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building hhsystem ui 1.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ ui --- [INFO] Deleting C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target [INFO] ------------------------------------------------------------------------ [INFO]

I'm wondering why I can't see following folders in src node in Package Explorer src/main/java src/main/resources src/test/java src/test/resources I can access those folders as direct children of the project and they exist in the file system. I'm using Spring Tool Suite (STS of Eclipse). Maybe I can configure Eclipse somehow ? Eclipse filters out folders that are marked as source from the "raw" folder path. That is, they are visible only as source folders: If you can't see them in either place, then they are either filtered out in the settings: check your settings for Package Explorer (the

I am using a fresh install of STS 3.8.3 and I am unable to add the JPA facet to an EJB project: If I try to create a JPA project, I cannot find that option: I am certain these used to be available in STS. What did I miss? We removed those extensions from the default distribution because users reported severe issues (search for JPA Event Handler on SO). In order to avoid this we decided to remove those tools from the distribution and added them to the extension install, so that you can get them back into STS quite easily. However, we can revisit that decision in the future, if those tools don't

This question already has an answer here: Deploying Maven project throws java.util.zip.ZipException: invalid LOC header (bad signature) 15 answers 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 of tc server and java home. Both use java 8. I cannot understand what the problem is. SEVERE: ContainerBase.addChild: start