What’s New in Spring 3.0? - Spring Enterprise Recipes: A Problem Solution Approach - page 71

At the time of this writing, the release is not considered final because Spring 3.0 is still being
developed and is still releasing 3.0 milestones. So the final .jar files are not on the central Maven
repositories. You need to download them from the SpringSource Enterprise Repository, which is a
special repository that SpringSource has established to provide access to Spring dependencies. One of
the main advantages of this repository is that it provides OSGi-friendly jars. If you're using Maven, the
configuration for the repositories looks like the following:

<repositories>
<repository>
<id>SpringSource Enterprise Bundle Repository - ➥

External Bundle Milestones</id>
<url> http://repository.springsource.com/maven/bundles/milestone</url>
</repository>
<repository>
<id>SpringSource Enterprise Bundle Repository - ➥
SpringSource Bundle Releases</id>
<url> http://repository.springsource.com/maven/bundles/release</url>
</repository>
<repository>
<id>SpringSource Enterprise Bundle Repository - ➥

External Bundle Releases</id>
<url> http://repository.springsource.com/maven/bundles/external</url>
</repository>
<repository>
<id>SpringSource Enterprise Bundle Repository - Library Milestones</id>
<url> http://repository.springsource.com/maven/libraries/milestone</url>
</repository>
</repositories>

Finally, to add the wrapper dependency to get most of the functionality you're likely to need,
simply add the following to your Maven POM ( pom.xml , the Maven “project object model”) inside the
dependencies element.

<dependency>
<groupId>org.springframework</groupId>
<artifactId>org.springframework.spring-library</artifactId>
<type>libd</type>
<version>3.0.0</version>
</dependency>...

2-2. Using Java 5 Syntax in Spring

Problem
Spring has always worked in Java 5, of course. Indeed, it even provided extra functionality that worked
only in Java 5, but it never exploited Java 5's features at the core of the framework. Some use cases
practically beg to be reworked for Java 5.You should be aware of some of these things going forward
because even though existing code shouldn't be broken, a lot of these new features are enticing and can
save you a lot of conceptual complexity (not to mention keystrokes!)