- Based on Eclipse 3.7 Indigo SR1
- Upgrade to Maven Eclipse 1.0 which provides a number of benefits including:
- Significant performance improvements
- Much smaller memory utilization
- Much more stable. (No more build loops or corrupt workspaces)
- Upgrade to STS 2.8 (plus a prompt to simplify installing STS on first start up)
- Support for Java 7 and Tomcat 7 in preparation for Stack 3.2
- Support for Runtime Class Reloading. Based on the Spring Loaded tool. Similar to JRebel (though not as mature) but free and integrated with the LDSTech Tomcat Server.
- Significant improvements in how the LDSTech Tomcat server manages your deploy configuration.
- The IDE will now automatically create and delete Tomcat servers for your projects as you import or remove them. We attempt to automatically choosing correct JVM and version of Tomcat for each project.
- Enabled automatic updates so you will automatically get fixes and new versions as we provide them. (Will check on every restart of the IDE)
- And much more: Full details can be found in our release notes
You need to do a full reinstall of the IDE because of the upgrade from eclipse 3.6 to 3.7. In addition, you will need to start with a brand new workspace and fresh checkouts of your application(s) thanks to the Maven Eclipse 1.0 upgrade.
On import you may also see some new errors generated by Maven Eclipse regarding m2e’s inability to know what to do with the goals of some maven plugins. Because of a change in the way Maven Eclipse 1.0 works some plugins that used to work fine may now need special help from an eclipse plugin to know how to do their job. If you run into a maven lifecycle/plugin goal error contact a member of the Stack team and we can look into creating a maven “configurer” to properly handle the situation.
If you use GWT because of some changes in the GWT Eclipse plugin you will need to add the following configuration to the plugins section of your web POM. It’s lame I know. We’re hoping Google will fix it soon:
Code: Select all
If you have any questions or experience any problems please contact a member of the Java Stack Team!