The Spring Blog

This is the third milestone release in the Spring 2.1 series, introducing autowiring for collections, the "bean(name)" pointcut element, various JDBC enhancements, JRuby 1.0 support and many refinements all over the framework.

Please see the changelog and JIRA roadmap for more details on the new features introduced in this release.

FYI, we have also released 2.0.7 snapshots, containing backported fixes from 2.1 M3. Please give a recent snapshot a try as a drop-in replacement for 2.0.5/2.0.6! The official 2.0.7 release is scheduled for August 15th.

After fixing approximately 250 bugs and working uncountable hours on adding support for Spring 2.0, Spring Web Flow, Spring AOP and Spring JavaConfig, we are proud to announce the immediate availability of Spring IDE 2.0.

Spring IDE 2.0 contains lots of new features and a bunch of bug fixes. A list of all closed tickets is available in our ticketing system. For those of you that are not familiar with recent development of Spring IDE here is a short list of features included:

We are pleased to announce that Spring 2.0.6 has been released. Spring 2.0.6 is a bugfix and enhancement release in the Spring 2.0 series, addressing all issues reported since 2.0.5 and backporting various refinements from 2.1 M2 (e.g. compatibility with JRuby 1.0).

The release candidate is available immediately from our developer update site at http://springide.org/updatesite_dev. Please take some time for testing and provide feedback on any errors, bugs or problems you might find. Many thanks to all that already provided feedback and bug reports. The feedback is really valuable for us.

This is the second release candidate of Spring-WS, a product of the Spring community focused on creating document-driven Web services. This release contains fixes for bugs discovered since the RC1 release along with minor improvements. In addition, the "Airline" sample application has been enhanced to use Java 5 features including the new @Endpoint programming model, JPA support, @Transactional, and more.

We are proud to announce that the first release candidate of Spring IDE 2.0 has been released. Read the announcement on the Spring IDE blog.

Spring IDE 2.0 contains lots of new features and a bunch of bug fixes. Most noteably we have added comprehensive support for Spring 2.0 namespace-based configurations, Spring AOP including @AspectJ-style aspects, Spring Web Flow and Spring JavaConfig.

The release candidate is available immediately from our developer update site at http://springide.org/updatesite_dev. Please take some time for testing and provide feedback on any errors, bugs or problems you might find. Many thanks to all that already provided feedback and bug reports. The feedback is really valuable for us.

This is the second milestone release in the Spring 2.1 series, introducing refinements in the annotation config support as well as support for AspectJ load-time weaving and various further new features.

This release also introduces a revised structure for Spring’s module jars, now prepared for OSGi. Note that Hibernate 2.1 support has been dropped: Spring generally requires Hibernate 3.1 or higher now.

We are pleased to announce that Spring 2.1 M1 has been released. This is the first milestone release in the Spring 2.1 series, introducing major new features including annotation-based configuration, JCA-based message endpoint management, new "context" and "jms" XML configuration namespaces, and JDK 1.6 and Java EE 5 support.

We are pleased to announce the first release candidate of Spring LDAP 1.2, with a number of features and bug fixes. Only the most important are listed here. For a complete listing, please see the changelog.The release is available for download here.

Implemented client-side transaction support for Spring LDAP. See reference documentation for further information (LDAP-29).

Changed the exception hierarchy to be an unchecked mirror of the JNDI NamingException hierarchy (LDAP-4).

Exceptions thrown by Spring LDAP are now always Serializable, regardless of whether the wrapped NamingException is (which is not always the case) (LDAP-14).

Rewrote LdapEncoder.nameDecode() to solve problem with national characters and remove regular expression used in parsing, drastically improving Distinguished Name parsing performance as a bonus (LDAP-30).