SpringSource - a disappointment

Well, tried for several hours to install and use springsource STS.

springsource used "almost every" technology @ their disposal:
- Maven
- Spring
- gwt
- spring roo
- jpa
- log4j
- AOP - AspectJ
- JUnit

Well, this should be great but
they forgot to make it compile and run -
a very very big OOPS.

Downfall summary:
- They introduced a new scripting language (roo)
- New annotation API (roo annotations)
- Complex
- Created a whole different eclipse plugin management solution of their own. Why?
- Have an installation process that takes about several hours.
- Their hello world doesn't compile on Eclipse and no instructions on how to compile and run it outside of Eclipse.

Bummer. Sounded so good when I first read about it...


  1. Sorry to hear that you had a problem getting STS installed. I install STS very frequently across multiple machines and have never had an install that took any near the "several hours" that you are reporting. The STS community forum is a great place to discuss any difficulties you may have encountered and there is also a very detailed installation guide as well. We are committed to making STS the best Spring development tool possible so I look forward to your feedback.

    Adam FitzGerald

  2. Adam, thank you for your point of view.

    You've linked to the installation guide, which is a 15 page guide - an example for the complexity I mentioned.

    There were other technologies that I reviewed that were indeed less complex and had less functionality than STS but at least had no problem running a hello world on them.
    Among them: Java :) GWT, Android, Google App Engine, Jetty, Tomcat and others.

    I think any product should stay as simple as possible.

    I'll check out STS's community forum to find solutions/explanations to what I thought were the downfalls of STS.