Does there need to be a statement made about the jakarta.* namespace being inapproriate for applications?

[starksm64]

Based on the platform dev thread "Jakarta TCK package naming convention":
https://www.eclipse.org/lists/jakartaee-platform-dev/msg03072.html

The only statement that exists regarding restrictions around package namespace is from the Servlet specification:

15.2.1. Web Application Class Loader
Servlet containers that are part of a Jakarta EE Platform product should not allow the application to
override Java SE or Jakarta EE platform classes, such as those in java., javax., and jakarta.*
namespaces, that either Java SE or Jakarta EE do not allow to be modified.

Specs also reference the Java Language Specification which has always called out the java.* and javax.* packages as special in the terms of license section:

"... (b) does not modify, subset, superset or otherwise extend the Licensor Name Space, or include
any public or protected packages, classes, Java interfaces, fields or methods within
the Licensor Name Space other than those required/authorized by the Specification
or Specifications being implemented; ..."

The question is, does there need to be a formal statement regarding the use of the jakarta.* package namespece, and associated requirements on TCK deployments?

Related:
jakartaee/rest#1081
https://www.eclipse.org/lists/eclipselink-dev/msg08182.html

[scottmarlow]

Also related:
jakartaee/jsonp-api#351

[starksm64]

Additional feedback from the EF regarding usage of their trademarks including the jakarta package:

1. See the Eclipse Foundation Trademark Usage Policy which says
   • Proper Usage of Eclipse Foundation Trademarks
     • “4. Only Eclipse Projects are authorized to develop or maintain software packages that use Eclipse Foundation namespaces such as 'org.eclipse' in their namespace. An important use of an Eclipse Trademark is the 'org.eclipse' string used on all namespaces for Eclipse Projects. This naming convention is used to identify code that has been developed as part of an Eclipse Project.”
   • Proper Usage of Eclipse WG Trademarks
     • "Use of any namespaces created by a WG including but not limited to ‘jakarta’, 'org.locationtech' or 'org.polarsys' is not permitted by this Policy unless authorized in advance in writing by Eclipse."
2. Also see the EF TCK License which says
   • "4.c. comply with any requirements stated in the Specification with regard to subsetting, supersetting, modifying or extending the Specification in any Product claimed to be compatible with the Specification."
3. Also see the (Jakarta) Compatibility Trademark License Agreement which says
   • “1.11 “Specification-Compatible Implementation” shall mean an implementation that: … (ii) does not modify, subset, superset or otherwise extend the Eclipse Name Space, or include any public or protected packages, classes, interfaces, fields, methods or constructors within the Eclipse Name Space, other than as required or authorized by the Ratified Specification.”

It is clear that users should not be creating applications under the jakarta package. It is unclear that TCK projects should not do so for legal reasons, but it does not look right to do so. The discussion on the specification call today was to approve the recommended TCK package name voted on by the platform dev community as the recommended package for TCK application deployments.

[lukasj]

Can it be clarified what the application and/or deployment is meant to be?

As of Jakarta EE 9.x some specs, like ie activation, xml binding and few others, have no restrictions on a package namespaces in which apps can be written other than those implied directly by JLS. XML binding spec for instance uses term XML Binding application to refer to everything having classes with XML Binding annotations on them saying that the entry point to the XML Binding application is a call to JAXBContext.newInstance(). Based on that XML WS specification API is currently clearly valid XML Binding application written in the jakarta package namespace (see jakarta.xml.ws.wsaddressing.W3CEndpointReference) and to cover this particular use-case, the TCK for the XML Binding Specification should contain a test in jakarta package namespace.

[starksm64]

From the specification committee discussion:

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.

[starksm64]

@lukasj The main issue is application deployments targeting application, web, ejb containers.

[starksm64]

Start of proposed statement for EE10:
https://docs.google.com/document/d/1eE1vioEL5QprKxEMwKFJkNUOsKdV7rHJyFLMGj96Abo/edit?usp=sharing