| Re: [jakarta.ee-spec.committee] Agenda for the January 12th Jakarta EE Specification Committee call |
| Can we add to the agenda for tomorrow a discussion/action item about explicitly disallowing people from creating or modifying classes under the jakarta.* namespace. I.e. can someone decide to write an application inside say jakarta.myapp.* or someone create and publish thier own original code or API in jakarta.* without going through the JESP. There is an explicit statement in the Java Language spec that explicitly says this is forbidden for java.* and javax.*. When we migrated to the jakarta.* namespace, we did not explicitly create a similar statement. The discussions on the Platform dev list would benefit from swift clarification here. The action item I recommend is we update the required boilerplate each spec must include so it has an explicit statement forbidding it. Here are a couple versions of text we can kick around: "The packages java, javax, and jakarta are reserved and trademarked. Applications should not create or modify classes under these packages. Applications that do so have unspecified behavior and may not deploy, function properly at runtime, or be portable." Or target jakarta.* specifically -- likely legally safer to avoid commenting on java and javax and let that get enforced elsewhere. "The jakarta.* package is reserved and trademarked by the Eclipse Foundation. It is forbidden to modify, subset, superset or otherwise extend this package without explicit permission from the Eclipse Foundation through the established Jakarta EE Specification Process. Applications that modify, subset, superset or otherwise extend this package have unspecified behavior and may not deploy, function properly at runtime, or be portable."
|