The Maven artifact jakarta.batch:specification:2.1.1 was wrongly released with some "2.2" version strings.
Note this has ZERO specification impact. The specification artifacts are governed by a whole separate process and were not updated by the 2.1.1 release (which was only done to update an OSGi header in the API JAR).
Naturally I only noticed this right after hitting the "Release" button to synch to Maven Central.
If you unzip the .zip artifact you'll see filenames:
jakarta-batch-spec-2.2.pdf/html and also right in Section 1. of the v2.1.1 spec it shows:
Version: 2.2
Status: DRAFT
Release: 2022-06-14
CAUSE
spec/pom.xml: 2.2</spec.version>
PURPOSE OF ISSUE
In case anyone else notices this, so they don't bother opening an issue
Maybe clean up better if we were to have to do this a next time?
The Maven artifact jakarta.batch:specification:2.1.1 was wrongly released with some "2.2" version strings.
Note this has ZERO specification impact. The specification artifacts are governed by a whole separate process and were not updated by the 2.1.1 release (which was only done to update an OSGi header in the API JAR).
Naturally I only noticed this right after hitting the "Release" button to synch to Maven Central.
If you unzip the .zip artifact you'll see filenames: jakarta-batch-spec-2.2.pdf/html and also right in Section 1. of the v2.1.1 spec it shows:
CAUSE
spec/pom.xml:2.2</spec.version>
PURPOSE OF ISSUE