From 0bc64d41763584f6526d3790c8b16585fc3580f0 Mon Sep 17 00:00:00 2001 From: dsyer Date: Sun, 12 Jul 2009 17:06:37 +0000 Subject: [PATCH] OPEN - issue BATCH-1336: Ping bamboo --- .../batch/core/launch/support/CommandLineJobRunner.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-batch-core/src/main/java/org/springframework/batch/core/launch/support/CommandLineJobRunner.java b/spring-batch-core/src/main/java/org/springframework/batch/core/launch/support/CommandLineJobRunner.java index 00d974cd5..ce74b7cbf 100644 --- a/spring-batch-core/src/main/java/org/springframework/batch/core/launch/support/CommandLineJobRunner.java +++ b/spring-batch-core/src/main/java/org/springframework/batch/core/launch/support/CommandLineJobRunner.java @@ -78,7 +78,7 @@ import org.springframework.util.StringUtils; * Notice a property is available to set the {@link SystemExiter}. This class is * used to exit from the main method, rather than calling System.exit() * directly. This is because unit testing a class the calls System.exit() is - * impossible without kicking off the test within a new Jvm, which it is + * impossible without kicking off the test within a new JVM, which it is * possible to do, however it is a complex solution, much more so than * strategizing the exiter. *