Upgrade to Spring 2.5.2
This commit is contained in:
2
pom.xml
2
pom.xml
@@ -81,7 +81,7 @@
|
||||
|
||||
<properties>
|
||||
<maven.test.failure.ignore>true</maven.test.failure.ignore>
|
||||
<spring.framework.version>2.5</spring.framework.version>
|
||||
<spring.framework.version>2.5.2</spring.framework.version>
|
||||
</properties>
|
||||
|
||||
<profiles>
|
||||
|
||||
@@ -40,11 +40,31 @@ mvn -o install -P fast
|
||||
is the quickest way to update your local repo (assuming the tests
|
||||
are OK). It is equivalent of setting <<<-Dmaven.test.skip=true>>>.
|
||||
|
||||
* Running Individual Tests
|
||||
|
||||
The standard way to do this with Maven is -Dtest= with the class name (not fully qualified), e.g.
|
||||
|
||||
+---
|
||||
$ mvn test -Dtest=FootballJobFunctionalTests
|
||||
+---
|
||||
|
||||
In the samples you can also add additional system properties, which will be used to override bean properties. This can be done with an argLine property, e.g.
|
||||
|
||||
+---
|
||||
$ mvn test -Dtest=FootballJobFunctionalTests -DargLine='-Dplayer.file.name=player.csv -Dgames.file.name=games.csv'
|
||||
+---
|
||||
|
||||
or by specifying forkMode=never (in which case the test is run in the same process as Maven):
|
||||
|
||||
+---
|
||||
$ mvn test -DforkMode=never -Dtest=FootballJobFunctionalTests -Dplayer.file.name=player.csv -Dgames.file.name=games.csv -Djob.commit.interval=50
|
||||
+---
|
||||
|
||||
* Eclipse IDE
|
||||
|
||||
Our policy is to commit Eclipse (and only Eclipse) meta data to
|
||||
source control. This will work out of the box for you if you use
|
||||
the (excellent) Q4 Eclipse-plugin
|
||||
the (excellent) Q4E Eclipse-plugin
|
||||
(http://q4e.googlecode.com/svn/trunk/updatesite). With this plugin,
|
||||
each of the reactor modules at the top level builds independently
|
||||
and feeds changes into other projects in your workspace. It is not
|
||||
|
||||
@@ -35,7 +35,7 @@ Spring Batch Features and Roadmap
|
||||
* ItemWriter abstraction and implementations for flat files and xml
|
||||
(the Sql case is just a regular Jdbc Dao).
|
||||
|
||||
* ItemReader and ItenWriter implementations are generally Skippable.
|
||||
* ItemReader and ItemWriter implementations are generally Skippable.
|
||||
Skippable means that they can be asked by clients to mark items as
|
||||
skipped, and not provide or process them next time they arrive.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user