I have spent the past two hours watching two Webinars about MyEclipse for Spring:
Based on viewing these two webinars, I conclude that the quality of MyEclipse for Spring and its meticulous attention to detail is breathtaking. My impression so far is that MyEclipse for Spring runs circles, dances, and does somersaults in a head to head comparison against STS and Roo.
A search for "MyEclipse for Spring" in the Spring Forums indicates it is completely off the radar, like a stealth bomber approaching so quickly and so silently that no one notices its approach.
Instead of spending this weekend studying further the Spring samples (all of which I have checked out from Subversion and successfully gotten to run in STS), I am instead going to download MyEclipse for Spring version 8.6 M2 and follow the "MyEclipse for Spring" tutorials at this link: http://www.myeclipseide.com/module-h...lay-pid-7.html
(Update1). I just discovered this link to MyEclipseForSpring's YouTube channel, currently containing 22 videos about MyEclipse for Spring: http://www.youtube.com/user/myeclipseforspring
(Update2). I have spent the last 5 hours battling various problems in MyEclipse for Spring and learning a great deal in the process. I have no doubt that when I return to STS and Roo, the knowledge gained from working with MyEclipse for Spring will transfer nicely. It's ironic that STS originally was going to cost $3,500 per developer but then the price was reduced to free. By contrast, MyEclipse for Spring is a reasonable $199 with a free 30 day trial. Maybe STS should be priced at $99 and in return for getting some green, STS could be better maintained and cared for, the way MyEclipse for Spring is.
(Update3). After a full 9 hour Saturday of working with MyEclipse for Spring (using Snow Leopard), I have it configured and working properly. The proof of that is that the I generated a GWT application backed by a Derby database, and it works perfectly. These are the advantages I see in MyEclipse for Spring:
1) With the click of checkbox, a Spring application can be generated as either Spring 2.5 or Spring 3.0
2) With the click of a checkbox, a Spring application can be generated to either use Maven, or not use Maven.
3) With the click of a checkbock, a non-Maven Spring app can be generated to contain all the jar files in the "lib" directory, or else access the jar files from a shared location. MyEclipse for Spring puts all the jar files in the specified location automatically.
4) MyEclipse for Spring has 2-way UML tooling. Can generate UML from java classes, and/or can generate java classes from UML.
5) MyEclipse for Spring can generate Spring Flex apps, Spring GWT apps, Spring WebFlow apps, and Spring Web MVC apps. Amazingly, it can generate all 4 at the same time, or any combination of the 4.
6) The java code and configuration files generated by MyEclipse for Spring adhere to "best practices". They look as if they were hand written by an expert Spring programmer.
7) When you listen to the MyEclipse for Spring webcasts and video, it is evident they really care about the developer and have a lot of empathy with the needs of developers. They seem to really understand how difficult it is for developers new to Spring to catch on, and they specifically designed MyEclipse for Spring to be easy to use as a vehicle to learn Spring best practices.