| Re: [agentic-ai-dev] Maven Coordinates/Package Names |
|
Can you clarify what you mean by Sonatype namespace?
Are you referring to Maven coordinates, the repository names, or something else?
I've already noted there's no rule I can find against the use of "jakarta.ai" as the Maven group ID.
I don't see how us using this would prevent any other project choosing to do so as well.
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).
My (very rough!) understanding of it is that each project gets their own staging repo, which we already have:
https://repo3.eclipse.org/#browse/browse:agentic-ai-maven2-staging
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:
The example repository name given in that pom largely echoes what we have in the staging repo ("agentic-ai-maven2-staging"):
"You must set the 'nexus.staging.repository' system property
For example, -Dnexus.staging.repository=data-maven2-staging on the command line
in order to use this profile."
So I don't think there's a naming conflict issue there.
From: agentic-ai-dev <agentic-ai-dev-bounces@xxxxxxxxxxx> on behalf of Piotr Żygieło via agentic-ai-dev <agentic-ai-dev@xxxxxxxxxxx>
Sent: 10 March 2026 17:11 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 Tue, 10 Mar 2026 at 17:26, Reza Rahman via agentic-ai-dev
<agentic-ai-dev@xxxxxxxxxxx> wrote: > > If the initial email and Andrew’s pretty thorough explanation is not sufficiently clear already, I suggest looking at the code. Not sure what you mean, as I'm talking about the future and that code does not exist yet. And perhaps there is also the case of understanding what is "namespace". The piece quoted by Andrew talks about some "namespace" but does not say anything about the namespace I talk about. And I mean ONLY namespace in Sonatype Portal sense, which is being used during deployment/publishing. This is, and will not be, reflected anywhere in the code at all. Of these two 1.a namespace on the sonatype side would be jakarta.ai. 1.b it would be several namespaces: jakarta.ai.jakarta.agentic-ai-api, jakarta.ai.jakarta-agentic-ai-tck, jakarta-agentic-ai-examples (which now are few already) which one is going to be? I still think that using one `jakarta.ai` as a Sonatype namespace is bad for the future. -- Piotrek _______________________________________________ agentic-ai-dev mailing list agentic-ai-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://accounts.eclipse.org |