Skip to main content
This revision made May 21, 2013 18:23, by ScottKurz

TCK Change History


Overview thoughts


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).

2013-05-17

  • Internal build id - 0522xx
  • Maven version - 1.0

Change contents


We updated the SigTest signature files

2013-04-22

  • Internal build id - 0422d
  • Maven version - 1.0-b28

This was the first delivery marked "Final Release".

Difference compared to previous revision

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). == 2013-05-17 * '''Internal build id''' - 0522xx * '''Maven version''' - 1.0

 
 
Close
loading
Please Confirm
Close