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

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

I thought the namespace used by Jakarta was just "jakarta" and everything under that is fair game - unless the process changed for the new Central portal you don't need to register a new namespace for each individual group ID under your namespace.

https://central.sonatype.org/publish/requirements/coordinates/#supported-code-hosting-services-for-personal-groupid

    "There is no need to create new tickets for new subgroups!

    When we grant permissions at the top-level groupId, like io.github.example, you can publish any components under that groupId or any sub-groups that look like io.github.example.mysubgroup1 or io.github.example.android.

    The same applies for owned domains, if you register com.example you will be able to publish any component under that groupId or any sub-group like com.example.mysubgroup1 or com.example.sdk.android.app."

As an aside I am personally a fan of a more specific namespace to keep things "boxed" as I see it being a bit more future proof against shenanigans (I prefer "jakarta.ai.agent" rather than "agentic" but that's an aside to my aside), though I'm not against the more general encompassing one.

--

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: 11 March 2026 10:58
To: agentic-ai developer discussions <agentic-ai-dev@xxxxxxxxxxx>
Cc: Piotr Żygieło <piotr.zygielo@xxxxxxxxx>
Subject: Re: [agentic-ai-dev] Maven Coordinates/Package Names

 

On Wed, 11 Mar 2026 at 10:46, Andrew Pielage via agentic-ai-dev <agentic-ai-dev@xxxxxxxxxxx> wrote:

Can you clarify what you mean by Sonatype namespace?

https://central.sonatype.org/register/namespace/

I'm not against using 'jakarta.ai' as the root name.

But I'm -1 on placing every agentic-ai-* artifact _directly_ in jakarta.ai

I'd never speak about that if not for:

    > all future AI work into one neat place such as jakarta-llm or jakarta-mcp

I understood from that LLM, MCP mentioned above and whatever else to be SEPARATE Specifications that do not exist NOW. Not under Agentic AI one that's preparing the field for itself and others.

Pretend there is LLM AI Specification right now. Noone from Agentic AI is participating there. It's a completely separate group of people. And this LLM AI Spec wants to publish its 'jakarta.ai:jakarta.llm-ai-api'. Depending on namespace partitioning - which I numbered 1a 1b previously - it's either

- 1a jakarta.ai - already claimed by Agentic AI, so it needs to be shared - and all sharing parties might publish to every subpath groupId/artifactId.For that reason I think this is unwanted to share namespace access between specs.

- 1b every single subpath is a new namespace (with plenty to come) - but it's not possible to publish to several namespaces in one go. For that reason I think this is unwanted as well.

Thus I propose to unflatten this a bit and have `jakarta.ai.agentic (or whatever)` as namespace and starting point for groupId.

Seeing that it bothers just me - I should blame myself for being unable to explain myself.

And as everybody is so happy with all the binding votes to be +1 - I'll need to accept that.

If you're referring to the repository name, I don't believe that's what we're talking about here and that has a separate process (which I don't know in detail ottomh).

Not about repository names.

 

My (very rough!) understanding of it is that each project gets their own staging repo,

Projects need not to use staging repo but can choose, and few do so already - to publish directly to Central.

which we already have: https://repo3.eclipse.org/#browse/browse:agentic-ai-maven2-staging

But even there the project will be able to publish only to specific namespace/groupIds.

 

The Jakarta EE / Eclipse EE4J staging repo is an aggregation of all of the individual staging repos, I don't think you upload to it directly: https://repo3.eclipse.org/#browse/browse:ee4j-staging

Past that, we're just into uploading to Maven Central, which is a separate process again but I believe is handled by the parent pom: 

But the parent pom says nothing about privileges to namespaces.

I've also created https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7254 to confirm that it's all fine.

-- 

Piotrek