[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] TCK package names
|
Hi Tom,
Did Jakarta EE declare the forbidden usage of java or javax? I thought it was forbidden by Oracle trademark anyway. I don't think it is within the control fo Jakarta EE. Do you have better suggestions to avoid the confusion?
Thanks
Emily
================
Emily Jiang
Java Champion
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
LinkedIn: https://www.linkedin.com/in/emilyfhjiang/
IBM 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: "Thomas Watson" <tjwatson@xxxxxxxxxx>
Sent by: "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
To: jakarta.ee-spec.committee@xxxxxxxxxxx
Cc:
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] TCK package names
Date: Wed, Feb 2, 2022 1:44 PM
> 4. Any other package name not starting with jakarta.* is permitted in Jakarta EE 10. My only nit is that this cannot be true because one cannot use javax.* or java.*. This seems almost too obvious to state, but perhaps we are best to make ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
> 4. Any other package name not starting with jakarta.* is permitted in Jakarta EE 10.
My only nit is that this cannot be true because one cannot use javax.* or java.*. This seems almost too obvious to state, but perhaps we are best to make it as clear as possible given the contentious nature of this topic.
Tom
----- Original message -----
From: "Emily Jiang" <EMIJIANG@xxxxxxxxxx>
Sent by: "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
To: jakarta.ee-spec.committee@xxxxxxxxxxx
Cc: jakarta.ee-spec.committee@xxxxxxxxxxx
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] TCK package names
Date: Wed, Feb 2, 2022 5:18 AM
Hi David, On Jan 31, 2022, at 3:43 AM, Emily Jiang <EMIJIANG@xxxxxxxxxx> wrote: Package namespace decision is for future releases [Emily] > I think the proposed text is a good recap of the current understanding. However, I understood ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Hi David,
> I think the proposed text is a good recap of the current understanding. However, I understood the goal of the above action item to be more or less "what do we do after Jakarta EE 10?"
IIRC, during the conversation in our meeting, we said the new package namespace (ee.jakarta.tck.[spec]) can be used in the new releases such as Jakarta EE 10+. All of the existing packages remain unchanged. That was the interpretation for the task.
When it comes to names, normally it is difficult to work out the common-liked names. However, it seems some people showed desire of using the forbidden namespace jakarta.*. The first action is to get them off jakarta.* and offer alternative package name, ee.jakarta.tck.[spec]. However, some of them did not like this message based on yesterday's platform call. Instead of focusing on the long term plan right now, it is best to focus on explaining the reason and settle the argument.
As for Jakarta EE 11+, I am wondering whether we just let them to choose anything they want except jakarta.* if they don't like ee.jakarta.tck.[spec] or we open up for a wider conversation to collect the possible package names and ask the community to vote. I think no matter what name we choose will upset some people. Not sure whether this exercise is worthwhile.
To settle the current argument on why jakarta.* is forbidden for the TCK usage, we need to send a clear message to the community and explain why. I have added a couple of sentences to explain the reason based on Scott Marlow's feedback. I think the following message also aligns with Scott Stark's wiki.
1. The usage of jakarta.* as Jakarta EE TCK package names is NOT permitted in any of Jakarta EE releases. If some TCK tests use jakarta.* namespace, they can easily be challenged as invalid because jakarta.* was reserved for Jakarta EE API usage only. The challenge would be valid and the risk of getting the TCKs excluded would be very high.
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 take a further look at the bulletin point 1 to make the reason clearer and stronger.
Thanks
Emily
================
Emily Jiang
Java Champion
STSM, Jakarta and MicroProfile Architect @IBM
Liberty Cloud Native Architect & Advocate
IBM 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: "David Blevins" <dblevins@xxxxxxxxxxxxx>
Sent by: "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
To: "Jakarta specification committee" <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] TCK package names
Date: Tue, Feb 1, 2022 8:24 PM
I think the proposed text is a good recap of the current understanding. However, I understood the goal of the above action item to be more or less "what do we do after Jakarta EE 10?"
Do we want to work on what the plan would be for Jakarta EE 11 and onwards?
-David
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
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
