Re: [agentic-ai-dev] Maven Coordinates/Package Names

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

I had a quick scan through the JESP (https://jakarta.ee/about/jesp/) and EFSP (https://www.eclipse.org/projects/efsp/efsp_1.3/) and didn't find much around specific maven coordinate rules.

Only the following in the JESP:

"All development that modifies content in the javax namespace must be moved to a jakarta namespace. All jakarta namespace development must occur within the scope of a Specification Project operating under the purview of the Jakarta EE Working Group’s Specification Committee and must implement the process as defined by the most recently adopted revision of the JESP.
Use of the jakarta namespace is limited to API artifacts (all API jars, javadoc, and schema namespaces).
It must not be used for any deployment, including applications, TCKs, tools, libraries or any other assets produced by Specification Projects."

The review checklist (https://github.com/jakartaee/specifications/blob/master/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md) does make a couple of allusions to it, but it's not particularly explicit:

Include the following in the PR:
- [ ] A directory in the form wombat/x.y where x.y is the release major.minor version, and the directory contains the following.
- [ ] Specification PDF in the form of jakarta-wombat-spec-x.y.pdf
- [ ] Specification HTML in the form of jakarta-wombat-spec-x.y.html
...

1. Spec PR
...
  - [ ] Directory of form {spec}/x.y
  - [ ] PDF of form jakarta-{spec}-spec-x.y.pdf ("-spec" preferred but not required)
  - [ ] HTML of form jakarta-{spec}-spec-x.y.html ("-spec" preferred but not required)
  - [ ] Index page {spec}/x.y/_index.md following [template](https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md)
  - [ ] Index page {spec}/_index.md following [template](https://github.com/jakartaee/specification-committee/blob/master/spec_index_template.md)
...
  - [ ] Staging repository link of the form https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/{spec}/jakarta.{spec}-api/x.y.z/
...
  - [ ] Link to final TCK download zip file of the form https://download.eclipse.org/jakartaee/{spec}/x.y/*{spec}-tck-x.y.z.zip (The folder path is required, the file name pattern is preferred.)
  - [ ] Link to API jar file of the form https://central.sonatype.com/artifact/jakarta.{spec}/jakarta.{spec}-api/x.y.z/jar

At first reading I would take ${spec} to be the kebab-case (agentic-ai) or dotted-case (agentic.ai) format of the spec name, but there are examples of specs not following that rule e.g. CDI (jakarta.enterprise), and Soap with Attachments (jakarta.xml.soap)

So unless I'm overlooking something there's no explicit naming rules for maven coordinates on the side of the spec committee that would prevent using jakarta.ai as the group ID

--

Andrew Pielage
Senior Software Engineer

---

From: agentic-ai-dev <agentic-ai-dev-bounces@xxxxxxxxxxx> on behalf of Piotr Żygieło via agentic-ai-dev <agentic-ai-dev@xxxxxxxxxxx>
Sent: 08 March 2026 14:11
To: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Cc: Piotr Żygieło <piotr.zygielo@xxxxxxxxx>; agentic-ai developer discussions <agentic-ai-dev@xxxxxxxxxxx>
Subject: Re: [agentic-ai-dev] Maven Coordinates/Package Names

 

Hi Ivar,

> I don’t think there’s really a permissions issue of some sort. I suspect Ivar would have told us if there was.

Could you please check
https://www.eclipse.org/lists/agentic-ai-dev/msg00009.html
and confirm that there is no permissions issue of some sort waiting to hit?

What about _future_ specs that would like to be placed in jakarta.ai namespace?

> and see what the spec committee says

I just hope the spec committee is going to speak BEFORE something
lands in Central, when it will be harder to solve for the future.

--
Piotrek
_______________________________________________
agentic-ai-dev mailing list
agentic-ai-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org