| Re: [jakarta.ee-spec.committee] TCK package names |
>#1 is clear and does forbid TCK testing of certain cases that have been discussed as valid, which means in the future, such TCK tests if added, can easily be challenged as invalid (e.g. someone adding a TCK test that requires WEB containers to deploy apps that contain SPEC API classes would be challenged as invalid).
> #2 seems ambiguous and conflicts with #1, consider letting #1 define the rule instead of making exceptions for older EE version TCKs to use jakarta namespace.
> #3 seems to state that use of ee.jakarta.tck.[spec] is optional (e.g. such a name is approved but not required, which I think implies optional).
#4 remove the text "in Jakarta EE 10" as #4 currently contradicts the currently stated #3.
Because of the usage of "ee.jakarta.tck.[spec] is optional, any package names not starting with jakarta.* are permitted in Jakarta EE 10 TCK. I wanted to mention Jakarta EE 10 as we might want to reinforce a tck package name in EE 11.----- Original message -----
From: "Scott Marlow" <smarlow@xxxxxxxxxx>
To: "Jakarta specification committee" <jakarta.ee-spec.committee@xxxxxxxxxxx>, "Emily Jiang" <EMIJIANG@xxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] TCK package names
Date: Mon, Jan 31, 2022 2:51 PM
This Message Is From an External SenderThis message came from outside your organization.
> 1. The usage of jakarta.* as Jakarta EE TCK package names is NOT permitted in any of Jakarta EE releases.> 2. If a newly written Jakarta EE 10 TCK uses jakarta.*, they MUST be renamed to a package not starting with jakarta.*> 3. The recent approved TCK package name ee.jakarta.tck.[spec] can be used by Jakarta EE TCKs but the usage is not required.> 4. Any other package name not starting with jakarta.* is permitted in Jakarta EE 10.#1 is clear and does forbid TCK testing of certain cases that have been discussed as valid, which means in the future, such TCK tests if added, can easily be challenged as invalid (e.g. someone adding a TCK test that requires WEB containers to deploy apps that contain SPEC API classes would be challenged as invalid).
#2 seems ambiguous and conflicts with #1, consider letting #1 define the rule instead of making exceptions for older EE version TCKs to use jakarta namespace.
#3 seems to state that use of ee.jakarta.tck.[spec] is optional (e.g. such a name is approved but not required, which I think implies optional).
#4 remove the text "in Jakarta EE 10" as #4 currently contradicts the currently stated #3.
Thanks
ScottOn 1/31/22 6:43 AM, Emily Jiang wrote:I have not received any feedback regarding the proposed text. What does it mean? Do I have to hold it untill someone said it is okay to post it? I feel this is not an efficient process. We need to look into this in the next meeting.Thanks
Emily
================
Emily Jiang
Java ChampionSTSM, Jakarta and MicroProfile Architect @IBMLiberty Cloud Native Architect & AdvocateIBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU----- Original message -----
From: Emily Jiang/UK/IBM
To: jakarta.ee-spec.committee@xxxxxxxxxxx
Cc:
Subject: TCK package names
Date: Wed, Jan 26, 2022 10:39 PM
Below is the response to clarify the following confusion.
Confusion around what was decided regarding TCK package names and how it is to be applied to spec projects in Jakarta EE 10, and subsequent releases was not provided
Package namespace decision is for future releases [Emily]
===========In the recent TCK package name discussions, it seems that there was confusion around what was decided regarding TCK package names and how it is to be applied to specification projects in Jakarta EE 10 and subsequent releases.Jakarta Spec committer discussed this in this week's spec committee call. Below is the clarification.1. The usage of jakarta.* as Jakarta EE TCK package names is NOT permitted in any of Jakarta EE releases.2. If a newly written Jakarta EE 10 TCK uses jakarta.*, they MUST be renamed to a package not starting with jakarta.*3. The recent approved TCK package name ee.jakarta.tck.[spec] can be used by Jakarta EE TCKs but the usage is not required.4. Any other package name not starting with jakarta.* is permitted in Jakarta EE 10.Please let me know if you have comments.By the way, after this is approved, should we send to jakarta platform and tck mailinglist? any other mailing list?Thanks
Emily
================
Emily Jiang
Java ChampionSTSM, Jakarta and MicroProfile Architect @IBMLiberty Cloud Native Architect & AdvocateIBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee