- When you try to save a file, it kicks off the Spring Project Builder first (i.e. before the actual save takes place).
- The Spring Project Builder appears to hang for quite a while (minutes).
"pool-1-thread-29" prio=6 tid=0x4f244c00 nid=0x1220 runnable [0x4c5ce000] java.lang.Thread.State: RUNNABLE at java.util.zip.ZipFile.getNextEntry(Native Method) at java.util.zip.ZipFile.access$400(ZipFile.java:29) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:313) - locked <0x04197f10> (a java.util.jar.JarFile) at java.util.zip.ZipFile$2.nextElement(ZipFile.java:299) at java.util.jar.JarFile$1.nextElement(JarFile.java:223) at java.util.jar.JarFile$1.nextElement(JarFile.java:218) at org.springframework.ide.eclipse.core.io.ResourceUtils.addJarEntryResources(ResourceUtils.java:389) at org.springframework.ide.eclipse.core.io.ResourceUtils.getResourceForProject(ResourceUtils.java:358) at org.springframework.ide.eclipse.core.io.ResourceUtils.getResource(ResourceUtils.java:290)The problem is in the builder. It is re-scanning all your jar files and working out if everything is ok. The more jars you have the longer it takes. I understand that the root cause of the problem is the algorithm for resolving <import>’s (when parsing the XML in the WEB-INF configuration) which is not clever at all. The trouble with SpringSource is that they don’t release any dates on when things are due to be released. “It’ll be ready, when it’s ready” just doesn’t cut it when it comes to planning production environments. You have to start using what there is available in order to get all the testing done in time for our release date. We don’t get the chance to keep adding delays. I digress. Fear not friends, there is a solution, you can switch off the Spring Project Builder. It is a per project thing so you have to do it for all projects but it’s no biggie.
- Select the project in the Package Explorer.
- From the menu bar select Project->Properties
- From the left hand list select Builders.
- Uncheck Spring Project Builder.
- Click Ok.
Comment from: [Member]
I think that’s a little harsh. The good thing it does is produce an Eclipse with everything you need to write JEE applications. The Eclipse JEE doesn’t have any stuff to represent your object model graphically like STS does. STS also contains a lot of the stuff that you would normally have to download and install yourself. I’ve tried this before and you just get into dependency hell. You can be sure that everything that comes in that version works together.
I wrote the article when I was using STS 2.3. They are now on STS 2.6 which uses the Eclipse 3.6.2 platform.
So let’s hope it’s better!
Comment from: Bigamy [Visitor]
Comment from: pk [Visitor]
Form is loading...