The current GA release is 2.2.7.RELEASE, the latest snapshots are 3.0.0.BUILD-SNAPSHOT. The version 2.0.x and 1.x branches are now in maintenance (the last release was 2.0.4.RELEASE).
Traditional "spring-*" artifacts are deployed on the Maven central repo. Full releases in this format also go in our s3 repository, browseable here:
<repository> <id>spring-releases</id> <name>Spring Maven RELEASE Repository</name> <url>http://repo.springsource.org/release</url> </repository>
You can see the internal and external project dependencies in the spring-batch-*/*.pom files and also in the dependency reports for each module on this website. You will probably need spring-batch-core and spring-batch-infrastructure. Source code is packaged in a separate jar file in the same directory, and the samples are also bundled in the same way.
Individual dependencies can then by added like so (inside a <dependencies> element at the top level):
<dependency> <groupId>org.springframework.batch</groupId> <artifactId>spring-batch-core</artifactId> <version>2.2.7.RELEASE</version> </dependency>
All releases are also published in the SpringSource Enterprise Repository, searchable here and browseable here. The repository is segregrated by release, milestone and snaphot releases. For full releases use these repositories:
<repository> <id>com.springsource.repository.bundles.release</id> <name>SpringSource Enterprise Bundle Repository - SpringSource Bundle Releases</name> <url>http://repository.springsource.com/maven/bundles/release</url> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>com.springsource.repository.bundles.external</id> <name>SpringSource Enterprise Bundle Repository - External Bundle Releases</name> <url>http://repository.springsource.com/maven/bundles/external</url> <snapshots> <enabled>false</enabled> </snapshots> </repository>
In the SpringSource Enterprise Repository the artifacts have long, Java-package-like names: org.springframework.batch.core, org.springframework.batch.infrastructure and org.springframework.batch.test. They have dependencies which are in the same style, and are transitively complete within the same repository. So individual dependencies can by added like so (inside a <dependencies> element at the top level):
<dependency> <groupId>org.springframework.batch</groupId> <artifactId>org.springframework.batch.core</artifactId> <version>2.2.7.RELEASE</version> </dependency>
These builds are provided for evaluation and community feedback. Spring Batch builds have a release identifier ending in "MX" where X is the milestone number, or "RCX" for a release candidate (older builds have "mX" and "rcX").
You can find the .ZIP downloads of the milestones here.
Milestones also published in the s3 repository with Maven Central format dependencies browseable here. To use them, just add the following repository to your POM (inside a <repositories> element at the top level):
<repository> <id>spring-s3</id> <name>Spring Maven MILESTONE Repository</name> <url>http://maven.springframework.org/milestone</url> </repository>
Then individual dependencies can then by added like so (inside a <dependencies> element at the top level):
<dependency> <groupId>org.springframework.batch</groupId> <artifactId>spring-batch-core</artifactId> <version>2.2.7.RELEASE</version> </dependency>
Milestones are also deployed to the SpringSource Enterprise Repository (browseable here), so use this repository if you want to depend on artifacts in the org.springframework.* style:
<repository> <id>com.springsource.repository.bundles.milestone</id> <name>SpringSource Enterprise Bundle Repository - SpringSource Bundle Milestones</name> <url>http://repository.springsource.com/maven/bundles/milestone</url> <snapshots> <enabled>false</enabled> </snapshots> </repository>
Then individual dependencies can by added like so (inside a <dependencies> element at the top level):
<dependency> <groupId>org.springframework.batch</groupId> <artifactId>org.springframework.batch.core</artifactId> <version>2.2.7.RELEASE</version> </dependency>
Nightly snapshots are available through the same process with slightly different URLs. See here for details.