Originally Posted by
Martin Lippert
The "S" indicates the Spring nature of a project, but that shouldn't be added automatically for each project as long as there is no Spring involved. Do you use Spring in those projects? But it does sound like a bug that this nature got added automatically after you upgraded from 2.9.1 to 2.9.2. Can you send my such a project before it got updated? Maybe I can reproduce this issue somehow.
Yes, I'm using it, and with that I mean there's a context xml file, and I use Spring components (classes, annotations, etc); but I do not use any Spring related tool in the IDE directly (no perspectives, and such).
I'm sorry but - apart from being a commercial project - I have more than 70 projects in the workspace, and it would be impossible to get a stripped down version of anything 
Now that I recall a bit more, after moving to 2.9.2 all the projects stated that the Maven configuration was out of date, and that I had to update it. I guess the "S" replaced the original "J" after that.
Originally Posted by
Martin Lippert
Regarding the slowdown: The Spring nature does indeed add additional functionality that is executed during a build. However, this should not cause your build to run for half an hour or so. I can see disc access in the thread dumps. Is your workspace on a local hard drive or on a network-attached storage? That could cause those slowdowns...
Everything is local, from the workspace to the Maven local repository.
This is the beginning of the context file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:p="http://www.springframework.org/schema/p"
xmlns:util="http://www.springframework.org/schema/util"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-3.0.xsd
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd">
<context:property-placeholder location="classpath:jdbc.properties"/>
<context:annotation-config/>
<context:component-scan base-package="my.web"/>
Could there be something that makes STS to stop by?
To add something more, I just reopened 2.9.2, cleaned the workspace and built everything.
And it tells that "Project configuration is not up-to-date with pom.xml. Run project configuration update" on every project.
And a bit more: going back to 2.9.1, after a clean and a build, all the projects maintained that "configuration not up-to-date", but after Maven -> Update Project Configuration everything is ok.
Reply With Quote
sts2.9.2 installation problem
