I haven't tried STS, but if possible I'd rather use a stock Eclipse (J2EE)
version through which I than install the needed plugins myself.
Meaning: not more than I actually need.
There seems to be a trend nowadays to provide "prepackaged" versions of Eclipse,
like this STS, but in the end you either get way too much (bloat) and still not
enough because your requirements don't 100% match their canned solution.
Anyway, STS might be cool and I probably check it out shortly but I'll then try
to install only the plugins I'm interested it. The (Spring) OSGi development,
Spring tc Server and VMWare integration features I'd rather have not
pre-installed.
On 04/25/2011 01:53 PM, Franklin, Matthew B. wrote:
Spring Tool Suite (STS) is a customized version of Eclipse. If I were to
use Eclipse for this project, I would probably use STS.
-Matt
On 4/24/11 4:38 PM, "Ross Gardler"<[email protected]> wrote:
I'm new to Spring (well, I've not coded anything in Spring for 5 years,
so that counts as new - nothing seems like it used to). Whilst the code
is in such an early form I thought I'd hack around to get to grips with
the basics.
In researching the Spring MVC stuff I found the SpringSource Developer
Tools [1]. Should I be bothering with this toolset?
[1[
http://www.springsource.com/landing/best-development-tool-enterprise-java
