Spring IDE 2.0 M4 released

[Christian Dupuis]

Dear Spring Community,

We are pleased to announce that Spring IDE 2.0 M4 has been released. This is the fourth milestone on our way to 2.0 final, introducing new features and fixing a bunch of bugs since M3. The release is available from the Eclipse Update Manager update site.

M4 is the first version that is released under the terms of the Eclipse Public License v1.0. You can get some background information about the license change here.

Here is a list of the features and improvements:

General

• Changed license from Apache License 2.0 to Eclipse Public License 1.0 #550
• Spring Project Properties pages of Beans Support and Web Flow Support are combined under a common category page #525
• Enable/Disable Spring IDE's Project Builders per project on common Spring Project Properties page #540
• Improved integration with Eclipse's Project Explorer

AOP Support

• Improved performance and memory footprint of AOP reference model building #519, #552 and #553
• Fixed support for proxy-target-class configuration setting #581

Web Flow Support

• Added a validator for Web Flow files #500
• Added ability to link a Web Flow file to a Beans Config Set in addition to only a Beans Config #560
• Several bug fixes that came up after the first version of the graphical and XML Web Flow Editor

Please make sure that you provide us with your thoughts and feedback to help further improve Spring IDE on its way to 2.0 final. Enter your bug reports in our ticket system.

We are planning on having one release candidate release around the end of May and the final version of Spring IDE 2.0 ready around SpringOne.

There are two features that we want to add to Spring IDE before we go RC1: Support for Spring JavaConfig and integration with Mylar. Work on these two has already been started; check out the nightly builds in the coming days.

Cheers

Torsten & Christian

[Keith Donald]

Awesome! Great to see another milestone. I just tried out another nightly last night and was noticing it had progressed quite a bit since 2.0 M3.

One request for enhancement for the Web Flow Editor: currently its a little difficult to tell quickly what states are of what type (view-state, action-state, etc) in the graphical editor. Would it be possible to color-code and vary shapes? We use the convention of baby blue rectangles for view-state, DFD green rectangles for action-state, a lighter Spring green rounded rectangles for subflow-states, and yellowish triangles for decision state, and black round dots for end states. interface21's graphic artist could help suggest color codes to use, and I think we should consider conventions for state diagrams [or flowchart diagrams].

Keith