Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [BALLOT] Approve the Jakarta TCK package naming convention ee.jakarta.tck.[spec]

On 1/12/22 5:22 PM, Emily Jiang via wrote:

Greetings Jakarta EE Specification Committee.

After a long discussion on the naming convention of the Jakarta TCK namespaces, the Jakarta community chose the package name: ee.jakarta.tck.[spec]. 

I need your vote to approve the Jakarta TCK package name ee.jakarta.tck.[spec]

Per the process, this will be a seven-day ballot, ending on January 19, 2022, that requires a Super-majority positive vote of the Specification Committee members (note that there is no veto). Community input is welcome, but only votes cast by Specification Committee Representatives will be counted.

The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton, and Shandong Cvicse Middleware Co.), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members.

Specification Committee representatives, your vote is hereby requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.

-1 (community input) as the chosen package prefix `ee.jakarta.tck.[spec]` use of `ee` conflicts with the Platform TCK use of the `ee` package prefix to signify tests that are specifically for the Jakarta EE Platform (e.g. specifically not for SE tests).  The new Standalone TCKs will target SE + EE, it would be inconsistent to use the `ee` package for SE tests.

Certainly there will also be new Platform TCK tests added in the future and if they use this now recommended package prefix, it will be confusing to the future generation of TCK maintainers as to which TCK tests are for SE versus EE.  IMO, this works against our overall improve EE development process goal and I don't think that anyone intended to cause that type of problem but it is more that we are are trying to make a quick decision for the EE 10 release to avoid delays (as I understand it).

In summary, we shouldn't use EE in the package name for TCK tests that are written specifically for SE.  For examples, see current Persistence TCK source EE folder + Persistence TCK source SE folder. 




_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top