robokaso 96c48bcbc5 IN PROGRESS - issue BATCH-366: Do we still need StepInstance? ...

http://jira.springframework.org/browse/BATCH-366

Killed StepInstance - test coverage temporarily low due to commenting obsolete tests (but sample jobs work fine).

2008-02-19 15:41:26 +00:00

..

.settings

added a BatchResourceFactoryBean to fixedlengthImportJob and fixed a repository error it illuminated.

2008-01-28 15:41:43 +00:00

src

IN PROGRESS - issue BATCH-366: Do we still need StepInstance?

2008-02-19 15:41:26 +00:00

.classpath

OK, let's try the Q4 plugin (instead of M2). Comments anyone?

2008-01-03 16:11:10 +00:00

.project

Remove duplicate job name (causing failures in test suite)

2008-01-23 12:23:27 +00:00

.springBeans

BATCH-220:Moved SimpleJob (formerly simpleTaskletJob) to use the ChunkedStep

2008-02-14 22:19:28 +00:00

jalopy_customized.xml

Add spring-batch- to module directory names (so folks can use mvn eclipse:eclipse if they want to).

2007-12-10 21:23:48 +00:00

maven_checks_customized.xml

Add spring-batch- to module directory names (so folks can use mvn eclipse:eclipse if they want to).

2007-12-10 21:23:48 +00:00

pom.xml

[maven-release-plugin] prepare for next development iteration

2008-02-06 09:52:23 +00:00

server.properties

Add spring-batch- to module directory names (so folks can use mvn eclipse:eclipse if they want to).

2007-12-10 21:23:48 +00:00