Java Reference
In-Depth Information
3.
Move the
launch-context.xml
file so it's used by Spring Batch Admin to
override its components.
With Spring Batch, if you haven't noticed, the POM file that comes with the sample project you've
been working with builds with Spring version 2.5.6. Obviously, this is an older version of Spring. Spring
Batch runs fine with the newer Spring 3.0.x; and because Spring Batch Admin requires a newer version of
Spring, your first update to the POM file is to update the version of Spring you're using to 3.0.5.RELEASE,
as shown in Listing 6-19.
Listing 6-19.
Updated Properties in
pom.xml
...
<properties>
<maven.test.failure.ignore>true</maven.test.failure.ignore><spring.framework.version>3.0.
5.RELEASE</spring.framework.version>
<spring.batch.version>2.1.2.RELEASE</spring.batch.version>
<dependency.locations.enabled>false</dependency.locations.enabled>
</properties>
...
You need to make one other version change, to the AspectJ dependencies. Instead of the 1.5.4
dependencies that your shell came with, you need to use the newer 1.6.6 version. Finally, add the
dependencies to the Spring Batch Admin jar files. Listing 6-20 shows the new and updated dependencies
in
pom.xml
.
Listing 6-20.
New and Updated Dependencies
...
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>1.6.6</version>
</dependency>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjweaver</artifactId>
<version>1.6.6</version>
</dependency>
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-admin-manager</artifactId>
<version>1.2.0.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-admin-resources</artifactId>
<version>1.2.0.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-integration</artifactId>
<version>1.2.0.RELEASE</version>
