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 change history for details
The TCK Reference Guide is a PDF in the TCK zip at path: doc/jsr352-tck-reference-guide
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: 155, Failures: 0, Skips: 0 [testng] ===============================================
The fact that OSGi manifest changes are tagged as EE-only reflects the fact we haven't given much though to using OSGi with the SE distribution.
|EE||Adjust OSGi bundle names, numbers to align with Glassfish Maven<->OSGi artifact name mapping norms|
|EE||Update API OSGi manifest to include CDI imports|
|Both||Add package-level Javadoc info for API packages.||Both||Log JSL validation errors w/ logger.warning msg - GLASSFISH-20418||Both||Wasn't calling listeners on partitioned threads GLASSFISH-20440||Both||Remove extra chunk exception wrapper.||Both||Perform rollback after catching Throwable and do so in finally clause.||Both||Readers and writers are closed in chunk tran instead of new tran in rollback/exception cases|