Infrastructure changes in Spring 2.1-m2 - No Fluff Just Stuff

Infrastructure changes in Spring 2.1-m2

Posted by: Ben Hale on June 1, 2007

Ben Hale

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.

Ben Hale

About Ben Hale

Ben Hale leads Pivotal's efforts to constantly improve the Java experience on Cloud Foundry. Recently he has been working on the Cloud Foundry Java Buildpack with an eye to making it the best place to run Java applications, in the Cloud or otherwise.

Prior to working on Cloud Foundry, Ben worked on large-scale middleware management tools, tc Server, dm Server (OSGi), and Spring. If you go back far enough, he even worked on a network management and monitoring application, but will deny it when asked.

Why Attend the NFJS Tour?

  • » Cutting-Edge Technologies
  • » Agile Practices
  • » Peer Exchange

Current Topics:

  • Languages on the JVM: Scala, Groovy, Clojure
  • Enterprise Java
  • Core Java, Java 8
  • Agility
  • Testing: Geb, Spock, Easyb
  • REST
  • NoSQL: MongoDB, Cassandra
  • Hadoop
  • Spring 4
  • Cloud
  • Automation Tools: Gradle, Git, Jenkins, Sonar
  • HTML5, CSS3, AngularJS, jQuery, Usability
  • Mobile Apps - iPhone and Android
  • More...
Learn More »