Tag: spring tool suite

Spring Tool Suite 3.5.0上的Spring Roo项目: 我已经安装了Spring Tool Suite 3.5.0（STS）。我希望能够在STS中创建一个Spring Roo项目，就像之前版本的STS一样。选项Roo项目不在列出的项目类型中。如何在STS中创建Roo项目？

从所需的.class文件中间接引用: 我在STS中遇到以下错误：无法解析org.springframework.core.env.EnvironmentCapable类型。它是从所需的.class文件间接引用的

Spring STS挂起的原因是什么？: 有时一开始STS挂起。有可能找到原因吗？可能存在日志还是可能在调试模式下启动？我怎么能完全区分挂起和工作非常缓慢？谢谢。 PS怎么解决？

Spring Tool Suite 3.6.1不会更新: 在Eclipse Luna中更新Spring Tool Suite ，因为我关闭了下载Eclipse 3.7更新的选项，我收到以下错误： **An error occurred while collecting items to be installed session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.springsource.ide.eclipse.commons.quicksearch,3.6.1.201408250654-RELEASE No repository found containing: osgi.bundle,org.springsource.sts,3.6.1.201408250824-RELEASE No repository found containing: org.eclipse.update.feature,org.springsource.ide.eclipse.commons.quicksearch.feature,3.6.1.201408250654-RELEASE No repository found containing: org.eclipse.update.feature,org.springsource.sts,3.6.1.201408250824-RELEASE No repository found containing: binary,org.springsource.sts.ide.executable.win32.win32.x86_64,3.6.1.201408250824-RELEASE-e43 No repository found containing: org.eclipse.update.feature,org.springsource.sts.package,3.6.1.201408250824-RELEASE-e43 No repository found containing: […]

Spring Tool Suite（STS）3.5.0 – org.codehaus.groovy.eclipse在求解器中是未知的: STS 3.5.0存在问题 https://issuetracker.springsource.com/browse/STS-3792 org.codehaus.groovy.eclipse 2.9.0.xx-201403261719-e43j8在求解器中未知！这些是我修复它的步骤，它允许我使用eclipse市场

Eclipse在Maven更新期间抛出NullPointerException: 我已经和内部的Eclipse内部错误打了两天了。我正在运行Eclipse的最新Spring Tool Suite版本，我试图导入一系列现有的Maven项目。每当我这样做时，Eclipse都会抛出NullPointerException，但错误日志视图中没有可用的堆栈跟踪。如果我指示Eclipse更新Maven项目（Maven> Update Project），我会再次获得NullPointerException。这次，错误日志视图报告以下堆栈跟踪： java.lang.NullPointerException at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119) at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104) at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93) at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88) at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124) at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81) at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207) at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386) at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107) at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61) at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253) at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363) at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343) at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371) at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191) at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180) at […]

无法启动组件 – ZipException：无效的LOC标头（错误的签名）: 我经历过类似的post。我已经尝试了大多数这些解决方案，但无法摆脱我得到的错误。期待一些帮助。在我将maven dependancies添加到部署程序集之后出现此错误。我正在使用STS与Pivotal tc Server Development Edition v3.1。我已经检查了tc服务器和java home的版本。两者都使用java 8。我无法理解问题所在。 SEVERE: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/myProject]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:158) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:596) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1805) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.catalina.LifecycleException: […]