Hello all,
I am sending this email as a follow up to an action item from the 2024-02-13 Platform Dev meeting.
As release co-coordinator, I believe that for component specifications that are only doing a service release for EE 11, we should not be using the refactored TCKs. Instead, we should stick with
the same, non-refactored, TCKs we used for EE10.
Thanks,
Ed
| edburns@xxxxxxxxxxxxx | office: +1 954 727 1095
| Calendar Booking:
https://aka.ms/meetedburns
|
| Please don't feel obliged to read or reply to this e-mail outside
| of your normal working hours.
|
| Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Alwin Joseph via jakartaee-platform-dev
Sent: Wednesday, January 31, 2024 12:59 PM
To: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>; jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Cc: Alwin Joseph <alwin.joseph@xxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [jakartaee-tck-dev] [External] : Re: EE 11 + needed Standalone TCKs for component specification ballots ...
Arjan,
Not yet. The work to create an Enterprise Beans (Lite) standalone TCK was partially done in PR
https://github.com/jakartaee/platform-tck/pull/965 (Draft now).
This work was stopped when the focus had shifted to use refactored versions of the TCKs for EE11.
I suppose it would be better to generate a standalone version of ejb lite TCK after we refactor the ejb30/ejb32 tests in platform tck.
Thanks,
Alwin Joseph
Hi,
Is there already a standalone TCK for Enterprise Beans (Lite)? I remember we tried that as one of the first about a year ago, but it was quite difficult and the work back then was not completed as far as I can remember.
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].
- _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.
I also plan to refactor and stage the TCK for below spec using the sigtest-maven-plugin (for the only signature test) soon.
- 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. 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)
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
