* Upgrade to Jakarta EE 9
* Upgrade to Spring Framework 6
* Upgrade to Spring Integration 6
* Upgrade to Spring Data 3
* Upgrade to Spring AMQP 3
* Upgrade to Spring for Apache Kafka 3
LDIF support is still in progress waiting for the next
major version of Spring LDAP.
Closes#4027Closes#3656
Add EPUB output and make all four output formats have links to one another,
to enable discoverability and accessibility (for the folks who need a
particular format to help them read the document).
Before this commit, tests in this change set
were failing on MS Windows due to the file
comparison method which was based on file
content hash comparison. With this method,
differences between OS line endings
(LF vs CRLF) in generated json files produce
different hashes.
This commit uses a logical json comparison
based on the jsonassert library.
This commit updates the configuration to run unit tests
with maven-surefire-plugin and integration tests with
maven-failsafe-plugin. JSR-352 TCK tests are considered
as integration tests and are executed with other integration
tests (no need for a separate profile to run them).
Some unit tests were failing when integration tests were
skipped.. Those tests have been temporarily ignored.
* Added new module "spring-batch-jsr352-tck" containing a maven configuration
to run the TCK tests.
* Added new profile "jsr-352-tck" to run the TCK tests
* The TCK build relys on the following environment variables being set:
* JSR_352_TCK_LIBS = the directory used to store libraries used during the TCK execution
* JSR_352_TCK_HOME = the directory containing the pristine version of the JSR-352 TCK
* JSR_352_BATCH_IMPL_CLASSES = the : seperated jars to be used and passed to the
batch.impl.classes property of $JSR_352_TCK_HOME/jsr352-tck.properties. These are
typically the paths to the JAR's located in $JSR_352_TCK_LIBS
TCK tests can be invoked by activating the jsr-352-tck profile.
At this time, if any errors occur while invoking the TCK ant build, the maven build will
continue. See https://java.net/bugzilla/show_bug.cgi?id=5833 for more details. A work around
is to modify:
$JSR_352_TCK_HOME/build.xml adding the following after </testng> and before </target>
<fail if="tests.failed" message="JSR-352 TCK TESTS FAILED"/>
