+1 I any project outside of the wildfly/wildfly repository should be using
a different groupId.
James R. Perkins
Principal Software Engineer
Red Hat <
https://www.redhat.com/>
<
https://www.redhat.com/>
On Wed, Feb 26, 2025 at 6:53 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
Currently we have a number of different repos publishing artifacts
using
the 'org.wildfly' groupId with no further namespacing.
Going forward I don't think we should allow any other new repos to do
that. It leads to administrative hassles, e.g. with setting things up in
Nexus.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...