I’m lost in this conversation and surprised that we are jumping to voting so fast. I couldn’t find the driver for this change. I believe that less renaming is better for the platform. Renaming and especially renaming in TCKs is a big task.
Who is going to do this? I am not ready to assign people to it. Last time we changed names for Maven artifacts we introduced the package split problems we still suffering with. So, if you ask me -> NO RENAMING!
-- Dmitry
P.S.
Also, I don’t think that it’s up to the platform group to make this decision. TCKs are a part of specifications, so it must go through the spec committee to get approved.
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Emily Jiang via jakartaee-platform-dev
Sent: 10 January 2022 22:43
To: David Blevins <dblevins@xxxxxxxxxxxxx>
Cc: Emily Jiang <emijiang6@xxxxxxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [External] : Re: [jakartaee-platform-dev] Jakarta TCK package naming convention
Done. I thought from the conversation thread, the package name of org.jakartatck.* might have some complications. Anyway, I have added.
Can we add the org.jakartatck option to this?
|
Having trouble viewing or submitting this form?
|
|
|
|
|
|
|
I've invited you to fill out a form:
|
|
|
Jakarta
TCK package naming convention
|
|
|
For all new Jakarta TCKs, we need a naming convention. All TCKs for Jakarta EE 10, the requirement is not to use jakarta.*. From Jakarta EE 11, the naming convention
must be used.
|
|
The new Jakarta EE TCKs from Jakarta EE 11 must use the following naming convention. Pick your choice below.
-
( ) ee.jakarta.tck.[spec]
-
( ) tck.jakarta.[spec]
-
( ) org.eclipse.jakarta.tck.[spec]
|
|
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
--
