This page is no longer up to date. See the RI and TCK pages on GitHub . Otherwise it's left for historical purposes, and in case I misformatted or lost anything by mistake on the new pages.
The RI is packaged into distinct SE, EE distributions. The SE package is available as a zip download, while the EE distribution is available via Maven.
The only difference between the two versions is a pair of config files. The Java code is identical, though some classes, such as the function integrating with JTA via JNDI, will not be active "out of the box" on an SE platform.
These config files are
So this nets out to the fact that a given version of the SE RI zip should correspond to a specific set of EE RI artifacts in Maven, except with different values within the batch-config.properties and batch-services.properties files configuring the JSR 352 RI for SE and EE, respectively.See RI_ChangeHistory for change history and some fix details for post-final release changes.
Note the project was not developed primarily as an open-source project using Maven but rather part way through we decided to export via Maven. This explains the lack of conformance to typical Maven conventions and also the use of aggregation via the 'maven-shade-plugin'.
[testng] =============================================== [testng] JSR352 TCK SE [testng] Total tests run: 152, Failures: 0, Skips: 0 [testng] ===============================================
See GuideToTCKAndSpecBugTags for some details on how to interpret the open Bugzilla bug list, and understand which ones are under consideration for what type of action (e.g. spec update and/or TCK update, etc.)