Also, no org.wildfly.extras.*.

The wildfly-extras github org is largely meant to serve as an incubating space for stuff that may at some time move to the wildfly GH org. So putting 'extras' in the package name is taking something possibly temporary and putting it into something that's likely permanent.

On Thu, Feb 27, 2025 at 6:06 PM James Perkins <jperkins@redhat.com> wrote:

+1 I any project outside of the wildfly/wildfly repository should be using a different groupId.

James R. Perkins

Principal Software Engineer

Red Hat

On Wed, Feb 26, 2025 at 6:53 PM Brian Stansberry <brian.stansberry@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@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@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/E7XQW3WILVA2H4F4XEO5J6LBBHFO7D7R/

--

Brian Stansberry

Principal Architect, Red Hat JBoss EAP

WildFly Project Lead

He/Him/His

_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@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/WFTRQQIVJK5OTNW2FACEMSSZKFMXDSMG/