VMware offers training and certification to turbo-charge your progress.Learn more
There has been quite a bit of discussion over my recent announcement about Spring and Maven. The discussion is all very good and worthwhile, but I do want to clarify a couple of points that I made.
First and foremost, we are committed to supporting Spring users who are using Maven as their build system of choice. This means we will help ensure accurate POMs are available in the Maven repository with each Spring release starting with Spring 2.0 RC4. That is what the world's most most popular JIRA issue is all about. Nothing more.
The topic of Spring's own internal build system is a completely separate matter. What I want to clarify from my original post is we are evaluating Maven as the future build system for Spring. We are evaluating it alongside Ant+Ivy as well. As many of you have noted, Spring is a large project that touches many others and sports a highly-customized homegrown build system. You will find everything from Java 5 code that is optional on pre Java 5 systems, to dependencies that only apply if you are using certain classes. At this time we simply don't know enough to say for sure that Maven will meet Spring's needs, but we certainly are taking a responsible look at it.
I hope that this clears up some of the confusion.