Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update version numbers

Browse Source
This commit is contained in:
dsyer
2008-03-03 18:19:12 +00:00
parent d6a5e6bbd7
commit a4cb024882
4 changed files with 16 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/site/apt/downloads.apt
View File

@@ -7,11 +7,11 @@
Milestone Builds
These builds are provided for evaluation and community feedback. They will have a release identifier ending in "mX" where X is the milestone number. The current release is <<1.0.0.m4>>.
These builds are provided for evaluation and community feedback. They will have a release identifier ending in "mX" where X is the milestone number. The current release is <<1.0.0.m5>>.
* Zip Downloads
Starting with Spring Batch 1.0.0.m4 there are ZIP based artifacts that contain the release JARs. You can find those releases {{{http://static.springframework.org/downloads/nightly/milestone-download.php?project=BATCH}here}}. There are two ZIP files in the release. The first zip file is called <<<spring-batch-*-no-dependencies.zip>>>. This file contains only the JAR files for the release. The second zip file is called <<<spring-batch-*-with-dependencies.zip>>>. This file contains the JAR files for the release as well as all of the third-party dependencies for the release. In addition, this release contains the Spring Batch source code including the samples and their third-party dependencies as well.
There are ZIP based artifacts that contain the release JARs. You can find those releases {{{http://static.springframework.org/downloads/nightly/milestone-download.php?project=BATCH}here}}. There are two ZIP files in the release. The first zip file is called <<<spring-batch-*-no-dependencies.zip>>>. This file contains only the JAR files for the release. The second zip file is called <<<spring-batch-*-with-dependencies.zip>>>. This file contains the JAR files for the release as well as all of the third-party dependencies for the release. In addition, this release contains the Spring Batch source code including the samples and their third-party dependencies as well.
* Maven Artifacts
@@ -33,7 +33,7 @@ Milestone Builds
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-core</artifactId>
<version>1.0.0.m4</version>
<version>1.0.0.m5</version>
</dependency>
+---------------
@@ -43,7 +43,7 @@ Milestone Builds
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-execution</artifactId>
<version>1.0.0.m4</version>
<version>1.0.0.m5</version>
</dependency>
+---------------

2
src/site/apt/getting-started.apt
View File

@@ -9,8 +9,6 @@ Spring Batch Getting Started
A convenient way to get started quickly with Spring Batch is to run the samples which are packaged in the samples module. The source code for the samples (and the other modules) is available either from the {{{downloads.html}.Zip assembly}} or from {{{source-repository.html}Subversion}}.
These instructions work with the "m4" .Zip distribution.
* Using the .Zip Distribution
** With Eclipse and without Maven

2
src/site/apt/snapshots.apt
View File

@@ -27,7 +27,7 @@ Snapshot Builds
<dependency>
<groupId>org.springframework.batch</groupId>
<artifactId>spring-batch-core</artifactId>
<version>1.0.0.m4-SNAPSHOT</version>
<version>1.0.0.rc1-SNAPSHOT</version>
</dependency>
+---------------

22
src/site/fml/faq.fml
View File

@@ -8,7 +8,7 @@
correct?
</question>
<answer>
We expect m3, m4, rc1 before 1.0 final, so realistically
We expect rc1 before 1.0 final, so realistically
not soon. You can track the progress and planning in
JIRA
(http://opensource.atlassian.com/projects/spring/browse/BATCH).
@@ -27,8 +27,8 @@
</question>
<answer>
<p>
We are still in the milestone release phase (1.0-m4
is in the pipeline). This means that we are still
We are still in the milestone release phase (1.0-m5
is just out). This means that we are still
adding functionality that we want to be part of a
1.0 release. We do not rule out changes to package
and interface names in this phase, but that said we
@@ -62,14 +62,14 @@
</question>
<answer>
Multi-threaded execution in a single VM is perfectly
possible with 1.0 - but we recommend exercising caution
in the analysis of such requirements (is it really
necessary?). Several people have tried it and there are
some issues with restartability (plus the usual
documentation requests), but otherwise it should work.
With a little more effort starting in m4 it should work
even better, but we aren't planning to solve the
restartability problem until after 1.0.
possible with 1.0 - but we recommend exercising
caution in the analysis of such requirements (is it
really necessary?). Several people have tried it and
it works as long as the step is intrinsically
restartable (idempotent effectively). The parellel
job sample shows how it might work in practice - this
uses a "process indicator" pattern to mark input
records as complete, inside the business transaction.
</answer>
</faq>
<faq id="layers">