With Eclipse and without Maven

Similar instructions would apply to other IDEs.

• Download the "with-dependencies" package and unzip to create a directory spring-batch-<versionId>.
• Open Eclipse and make a workspace in the directory you just created.
• Import the samples project from the samples directory.
• Add all the jar files in the distribution as library dependencies (except spring-batch-samples-<versionId>.jar). There are jars in samples/lib and in sources/lib, including some duplicates.
• Force the workspace to build (e.g. Project -> Clean...)
• Run the unit tests in your project under src/test/java. N.B. the FootbalJobFunctionTests takes quite a long time to run.

You can get a pretty good idea about how to set up a job by examining the unit tests in the org.springframework.batch.sample package (in src/main/java) and the configuration in src/main/resources/jobs.

To launch a job from the command line instead of a unit test use the CommandLineJobRunner.main() method (see Javadocs included in that class).

With Maven on the Command Line

• Download the distribution as above.
• Then run Maven in the spring-batch-samples directory, e.g.

  $ cd spring-batch-samples
  $ mvn test
  ...
  

With Maven and Eclipse

• Download the distribution as above.
• Get the Q4E Eclipse-plugin (http://q4e.googlecode.com/svn/trunk/updatesite). If you can't or don't want to install this plugin, you can use the Maven Eclipse Plugin to create the classpath entries you need.
• Open Eclipse and create a workspace as for the non-Mavenized version.
• Import the samples project as above.
• The project should build cleanly without having to fix the dependencies. If it doesn't, make sure you are online, and maybe try building on the command line first to make sure all the dependencies are downloaded. See the building instructions if you run into difficulty.