# 9. Corrections found while writing this

[← Previous](08-skip-vs-restart.md) | [README](../README.md) | [Next: Resourceless vs. JDBC-backed →](10-resourceless-vs-jdbc.md)

Per the verification discipline this repository follows, here is what was wrong in an earlier
draft, and how it was caught — recorded honestly rather than silently fixed, because the
mistake is often as informative as the correct answer.

## "CommandLineJobRunner was removed in 6.0" — wrong, it is deprecated

A community-written Spring Batch 6.0 migration guide describes `CommandLineJobRunner` as removed
outright, in a list alongside classes that genuinely were deleted
(`ChunkListenerSupport`, `JobExecutionListenerSupport`, and others). An early draft of this
article repeated that claim. Checking the actual `spring-batch-core-6.0.5.jar` shows it is wrong:

```console
$ javap -verbose -cp spring-batch-core-6.0.5.jar org.springframework.batch.core.launch.support.CommandLineJobRunner | grep -A3 "^public class\|Deprecated"
public class org.springframework.batch.core.launch.support.CommandLineJobRunner
...
    Deprecated: true
    RuntimeVisibleAnnotations:
      0: #505(#506=s#507,#508=Z#509)
        java.lang.Deprecated(
          since="6.0"
          forRemoval=true
        )
```

Full transcript: [`docs/output/09-commandlinejobrunner-deprecated-not-removed.txt`](output/09-commandlinejobrunner-deprecated-not-removed.txt).
The class is present, loadable, and functional in 6.0.5 — it carries
`@Deprecated(since = "6.0", forRemoval = true)`, which means "stop using this, it will be
deleted in a future release," not "this is already gone." `CommandLineJobOperator` is the
replacement, and it does exist alongside it in the same package.

This is the article's own self-correction pass working as intended: a claim sourced from a
third-party summary of a migration guide, not from a primary artifact, was treated as unverified
until checked. The general rule this project follows (see the parent repository's process notes)
is that a migration guide's own prose is not itself a primary source for "removed vs.
deprecated" — the jar is.

## `RepeatStatus` package move, caught by the compiler rather than by reading docs

Writing [`BatchConfig.reportTasklet`](../src/main/java/com/ankurm/batch/config/BatchConfig.java),
the first draft imported `org.springframework.batch.core.repeat.RepeatStatus` — the
Spring Batch 5.x location, from memory and from older examples. `mvn -B -o compile` reported:

```
[ERROR] .../BatchConfig.java:[93,57] package org.springframework.batch.core.repeat does not exist
```

The fix was `org.springframework.batch.infrastructure.repeat.RepeatStatus`, matching the general
package reorganization covered in [chapter 2](02-anatomy-of-a-job.md). No migration guide was
consulted for this one; the compiler error was sufficient, which is the point — letting
`javac` tell you where an API moved is faster and more reliable than trying to remember or look
up a package reorganization table.

[Next: Resourceless vs. JDBC-backed →](10-resourceless-vs-jdbc.md)