This should be part of the wildfly-extras Maven Central pushes.

--------
(Jira issue created from this email thread)
David Hladky
3:25 PM
to me, Farah

Just if I understand it properly, the new groupId will also be part of wildfly-extras Maven Central pushes? If possible, can you, please a create issue in https://issues.redhat.com/browse/NEXUS ? Thank you.

David Hladky
Principal Software Engineer
DXP Application Development Team
mail: dhladky@redhat.com

28. 8. 2025 v 15:20, Kabir Khan <kkhan@redhat.com>:

Hi David Hladky,

We had some discussions a while ago about deploying my project from https://github.com/wildfly-extras/a2a-java-sdk-server-jakarta to the new Nexus. Those happened here.

I am going to take the advice to change the group Id from org.wildfly.extras.a2a to org.wildfly.a2a. I believe you might need to add some config on your side to propagate artifacts under that group Id to Maven Central?

Next, I am a bit unsure what the repository URL is. People mention I should use the wildfly-extras and wildfly-extras-staging repositories. And I see those in https://repository.jboss.org/nexus/#browse/browse.

Are the URLs for these:
https://repository.jboss.org/nexus/repository/wildfly-extras-staging/ and https://repository.jboss.org/nexus/repository/wildfly-staging/?

I am still reading through your Wiki page, so I think that is all for now

Thanks,

Kabir