This news just in from Arjen Poutsma's twitter feed: Spring 3.0.0.RC1 is now available.

Download | Javadoc API | Change Log

Thank you to all of the dedicated community members that have given feedback and identified issues. Please keep up the good work as we push toward GA.

Dear Spring Community,

I'm pleased to announce that the 1.0.1 maintenance release of Spring BlazeDS Integration, the open source solution for building Spring-powered RIAs with Adobe Flex, is now available.

Download | Reference Documentation | JavaDocs | Changelog

Along with a number of minor bug fixes and enhancements, we have done some restructuring of the popular Spring BlazeDS Test Drive bundled sample application to make it even easier to get up and running in a variety of different environments, and to bring some of the configuration elements further in line with what you might see in the near future in a SpringSource Tool Suite project creation template for Spring BlazeDS Integration projects. Also, we've enhanced the security example further to really show how having Spring Security so tightly integrated sets this solution apart from alternate approaches to securing Flex applications.

As always, I encourage anyone interested to get involved by trying out the release and giving us feedback in the community forum and Jira. We've been getting some great feedback from people having success with Spring BlazeDS Integration in their projects, and we look forward to hearing more about your experiences.

Lastly, for anyone headed to Adobe MAX 2009, be sure and check out the session I'll be co-presenting with Mark Fisher on "Integrating Spring with BlazeDS and LiveCycle Data Services" on Wednesday, October 7th at 2PM.

In Rob's dm Server Roadmap blog entry, last April, we introduced two new artefact types: “plan” and “configuration file”.

Here is a short screencast demonstrating configuration files, in particular we show how to reference them from a plan.

First, a small web application picks up properties from a configuration properties file—deployed separately from the application. Second, the application and the properties are placed in the repository and a plan is constructed and deployed which installs and starts both the web application and its properties in one step.

Configuration Properties (5:59)

• QuickTime Screencast (42.9 MB)

Source Code

Git - git://git.springsource.org…

The last 100 days have been extraordinary for Hyperic. The events over the last three months place Hyperic in the unique position to be part of defining the future of application deployment and management. First, we announced in May that we were joining forces with SpringSource to build the next great full lifecycle enterprise software company. Judging by the response from our community, customers, partners, and the press, our combined "Build – Run ‑ Manage" strategy was the right choice and something the market has been waiting for.  Next, just a few weeks ago in August and barely 90 days…

Since Andy's announcement of the early alpha version of a new and improved Groovy Eclipse plugin, we have received very good feedback from early adopters out of the Groovy and Grails community. Judging from comments and twitter buzz there really is a big interest in good quality Groovy language support on the Eclipse platform. Andy and Andrew made good progress during the last weeks and are heading towards an M1 release which is not far off; check out JIRA for more details on when to expect it.

We'd like to thank everybody who tried out the early version and took time to report problems and…

Today, we make another significant announcement. SpringSource is launching an enterprise Java cloud—SpringSource Cloud Foundry.

This initiative is a logical extension of our integrated Build/Run/Manage approach to unifying the application lifecycle, extending our vision of simplifying enterprise Java beyond the traditional data center. As cloud computing becomes more important, we want to ensure that Java developers can take full advantage of it. We believe that our leadership in Java development, coupled with our strength in the runtime and management phases, enables us to provide a…

This release got overshadowed by some of the recent news this week, but I want to tell the community that Spring 3.0.0.M4 is now available.

Download | Reference Documentation | Change Log

This release includes some documentation changes, updated OSGi manifest information, a number of other improvements, along with some small revisions to supported frameworks like Hibernate, Tiles and others. Thank you to all of the dedicated community members that have given feedback and identified issues.

If you want to understand at a strategic level what the implications of VMware’s recently announced acquisition of SpringSource are, there are several good sources, including Steve Herrod’s (CTO of VMware) blog post, Rod Johnson’s commentary, Paul Maritz’s press and analyst call, and Darryl Taft’s insightful piece in eWeek.

In this post I will focus more on what this all means at a technical level, to give you an idea of the kinds of capabilities you can look forward to.

Firstly, let me reiterate that nothing changes with respect to our open source projects and  SpringSource product offerings. Nothing changes that is, apart from the fact that we’ll have even more opportunity in the future to add exciting new features to them. Spring 3.0 is coming soon, and we just released milestone 4. dm Server is making rapid progress towards a 2.0 release, and we have some very cool stuff up our sleeves for a forthcoming release of tc Server. The Eclipse tool support for Groovy is generating masses of interest, Grails is pushing on towards a 1.2 release…

Today I want to share some exciting news. We have signed a definitive agreement with VMware, who will acquire SpringSource. Subject to regulatory approval, we expect the transaction to close in Q3. SpringSource will become a division within VMware. I will continue to lead SpringSource, reporting to VMware CEO Paul Maritz.

Today I would like to explain the vision and careful reasoning behind this deal: why it’s natural and logical; why it can lead to the creation of amazing technology that will immensely benefit users; why it’s good for Spring and other technologies SpringSource leads or contributes to; why it’s good for the Spring community…