Hi Scott,
I have staged the refactored standalone TCKs for below (EL & Server Pages) specs at [1] from the tckrefactor branch. The TCK runners are present at
[2].
Excellent, thank you Alwin!
- _expression_ Language 6.0 (part of Wave 2 with review Feb 29)
- Server Pages 4.0 (part of Wave 6 with revie April 27)
I have informed the respective spec teams to review the same. Any pending changes can be made in the tckrefactor branch of platform-tck before the
ballot.
Excellent, thank you!
I also plan to refactor and stage the TCK for below spec using the sigtest-maven-plugin (for the only signature test) soon.
+1 but keep in mind that we will be making an signature tooling change to exclude all JDK classes via a package exclude of all java.* + javax.* classes (I tried this already via the -IgnoreJDKClass signature test option but it didn't work so code changes are needed). An alternative could be to instead only include jakarta.* classes in signature testing.
We can stage again once we have updated the signature test tooling.
- Annotations 3.0 (part of Wave 1 with review Feb 29)
I see you have only included the updated specifications for EE11. For eg, below specs are not updated for EE11. Can we also release and generate new refactored TCKs for below to
be used for the EE11 ballot.
Good question, I think we want to prepare to be able to generate the refactored Standalone TCKs for specs that are not updated for EE 11 but where could we release those TCKs to? I think we would also need to answer if the TCK test refactoring changed the Standalone TCK tests beyond what is expected in a service release?
For the EE 11 Standalone TCKs, we also need a way to freeze the (refactored) Standalone TCK sources once the respective component Spec ballot completes. Currently the Standalone TCK test sources are mixed in with the Platform TCK test sources.
Scott
I see the refactoring work is in progress for both with open PRs.
- Jakarta Standard Tag Library 3.0 (Wave 6)
- Jakarta Messaging 3.1 (Wave 6)
[1]
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee11/staged/
[2]
https://github.com/jakartaee/platform-tck/tree/tckrefactor/glassfish-runner
The EE 11 release plan [1] shows various dates for the different Specification Waves [2]. Note that further changes to [1] are pending to be merged soon.
From [2] (see my added notes in [2]), I think we will need the Platform TCK to generate Standalone TCKs for:
-
Annotations 3.0 (part of Wave 1 with review Feb 29)
-
_expression_ Language 6.0 (part of Wave 2 with review Feb 29)
-
Persistence 3.2 (part of Wave 5 with review March 29)
-
Server Pages 4.0 (part of Wave 6 with review April 27)
-
WebSocket 2.2 (part of Wave 6 with review April 27)
Correction: Server Pages and WebSocket are part of wave 5.
Did I miss any EE 11 component specs ^ that the Platform TCK has to generate Standalone TCKs for?
Also "to do" before the Platform TCK produces any Standalone TCK releases is changing the (1.3) TCK Process [3] wording as mentioned in issue [4] as the current wording prohibits us from producing Java SE
only TCKs.
[2] Waves copied from [1] that use "Platform TCK" generated "Standalone TCKs" with my comments added
Wave 1
-
Jakarta Annotations 3.0 (TCK is generated from Platform TCK).
Wave 2
-
Jakarta _expression_ Language 6.0 (TCK is generated from Platform TCK).
Wave 5
-
Jakarta Persistence 3.2 (TCK is generated from refactored Platform TCK).
-
Jakarta Server Pages 4.0 (TCK is generated from refactored Platform TCK).
-
Jakarta WebSocket 2.2 (TCK is generated from refactored Platform TCK).
Wave 8
-
Jakarta Platform (Platform TCK is needed)
-
Jakarta Platform (Platform TCK is needed)
-
Jakarta Platform Core Profile (Core Profile TCK is needed)
