Infrastructure changes in Spring 2.1-m2

With the release of Spring 2.1-m2, some significant changes have been made to the infrastructure of the Spring distribution. Please see the announcement and changelog for the complete list of changes.
Distribution
The distribution has been trimmed from 26 JARs in 2.1-m1 to 17 JARs in 2.1-m2. Take a look at the changelog for the list of files that changed, but from the commit message, here's what's new:
- spring-context.jar includes JMX support and core remoting support (no spring-jmx and spring-remoting jars anymore)
- spring-orm.jar combines all ORM support packages (replaces spring-hibernate, spring-ibatis, spring-jdo, spring-jpa, and spring-toplink jars)
- spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures)
- renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now
- renamed spring-support.jar to spring-context-support.jar
- renamed spring-portlet.jar to spring-webmvc-portlet.jar
- module jar files contain module-specific "spring.handlers" and "spring.schemas" files now
Maven Artifacts
I'm also pleased to announce that starting with the 2.1-m2 release, each Spring module will now have source jars in the Maven repository. The 2.1-m2 Maven artifacts are located in a private snapshot repository at this point, but the final release will be in the main Maven repo. If you would like to start using 2.1-m2 in your Maven project add a repository location to your POM that points at https://springframework.svn.sourceforge.net/svnroot/springframework/repos/repo-snapshots/. If you are using any Maven IDE support, please also download the source jars and open any issues with them at our JIRA.
Created

Ismael Juma says:
Added on June 1st, 2007 at 6:41 am -QuoteThank you.
Ben Hale (blog author) says:
Added on June 1st, 2007 at 7:18 am -QuoteMy pleasure. I deal with the Spring Maven artifacts quite a bit, so I know your frustration.
Erwin Vervaet says:
Added on June 2nd, 2007 at 1:59 am -Quotespring-webmvc-portlet.jar??
That seems to be a bit of a strange name.
I take it spring-webmvc.jar is still there? Why not have a spring-portletmvc.jar?
-FoX- says:
Added on June 4th, 2007 at 4:50 am -QuoteWhy don't just include the portlet classes in the spring-web.jar?
Ben Hale (blog author) says:
Added on June 4th, 2007 at 7:45 am -QuoteOn June 4, 2007 at 4:50 am, -FoX- said:
Well this one is easier for me to answer than Erwin's. We've always made a distinction between our web support and our webmvc support. The -web jar contains all of the basic web support only. So for example, the DispatcherServlet goes there because it's not just used by MVC but also by the HttpInvoker, Hessian, and Burlap remoting support. Since the portlet support is really just another dialect of MVC, it made sense for it to go into a separate JAR as well.
I've sent an email off to Juergen to have him chime in on this comment thread, but he'll be on vacation for a little while longer. Stay tuned for some more clarification.
Colin Sampaleanu (blog author) says:
Added on June 5th, 2007 at 10:18 pm -QuoteI have to say I also prefer spring-portletmvc.jar to spring-webmvc-portlet.
Colin
Color me thrilled says:
Added on June 18th, 2007 at 11:56 am -Quote"I'm also pleased to announce that starting with the 2.1-m2 release, each Spring module will now have source jars in the Maven repository."
This is the single best thing you could have included in this release, I just found this when I was checking for any related info before contacting you guys about this very issue.
Thanks.