-
Notifications
You must be signed in to change notification settings - Fork 108
Jakarta EE 9 Platform TCK current handling of removed technologies and legacy schemas
The EE 9 (Full) Platform + Web profile specifications list the technologies that are required to be provided by implementations. The EE 9 (Full) Platform + Web profile specifications list the technologies that are optionally provided by implementations.
The Jakarta EE Platform TCK tests technologies that are either required or optional in the EE 9 release.
Removed technology tests could be moved to a new Standalone TCK (just need a volunteer + discussion of the required steps).
As per https://jakarta.ee/specifications/platform/9/platform-spec-9-SNAPSHOT.html#a3447, Jakarta Platform EE 9 implementations are required to support the DTDs and schemas specified for Jakarta EE Platform 8 + 9. Support for versions of DTDs/schemas prior to Jakarta EE 8 is optional. Also refer to the [1] vote.
The Jakarta EE Platform TCK only tests with DTDs/Schemas from EE 9 or EE 8. Tests that use DTDs/schemas that are earlier than EE 8 should be updated to use EE 8 or EE 9 DTDs/schemas. As mentioned in jakartaee-tck/issues/266 [2] we are removing tests that use schemas that are not required by Jakarta EE 8 + 9, as they are discovered.
[1] Email VOTE: backward compatibility for descriptor schemas https://www.eclipse.org/lists/jakartaee-platform-dev/msg01400.html which initiated the voting on how Jakarta EE 9 schemas are to be handled [2] Update lib/schemas references (e.g. install, release, tests under src) to use either EE 9 or Jakarta EE 8 schemas (as per Jan 21, 2020 VOTE: backward compatibility for descriptor schemas). Also drop unused lib/schemas + lib/dtds https://github.com/eclipse-ee4j/jakartaee-tck/issues/266