TCK Change History
The Technology Compatibility Kit (TCK) should be updated more carefully than the RI, since we want to avoid the situation where a change breaks an implementation that had been running successfully (passing all tests) against a previous version of the TCK.
This might apply even if the fix is a "bug" in that the test logic clearly contradicts the intentions and behaviors stated in the specification. On the other hand changes like improving diagnostics and making the TCK more configurable and user-friendly should be able to be made without this type of concern.
We intend to make changes on a case-by-case basis, and deal with the above risk by:
- Providing an explanation and justification for each change in the change history text on this page
- Preserving the old versions of the JSR 352 TCK zips and continuing to make them available for download
NOTE on Maven version
The TCK isn't primarily delivered via Maven but rather via the download zip. The Maven version is included for identifying correspondences to other updates, and does not imply you should pick up the TCK from Maven (although some artifacts are indeed delivered to Maven).
- (No update to TCK reference guide or other instructions).
- Fixed batch.xml, removing extraneous entries for classes that weren't even batch artifacts.
- (No need to update the TCK reference guide or other instructions as in the earlier change).
Major Changes (affects test pass/failure)
- Updated the SigTest signature files for @Nonbinding issue. There is an associated change to the command needed to execute the signature tests (in short, the @Nonbinding class needs to be made available on the signature test execution classpath, e.g. via the CDI API jar). See change history within TCK Reference Guide for more detail on this issue.
- Added/improved Javadoc especially the TCK "porting package" SPI
This was the first delivery marked "Final Release".