2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev December 2025

wildfly-dev@lists.jboss.org

6 participants
29 discussions

Start a nNew thread

Use of the 'org.wildfly' groupId

by Brian Stansberry

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

3 weeks, 2 days

7
16
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

1 month

3
13
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

2 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

2 months, 1 week

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

2 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

2 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

2 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

2 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

2 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

2 months, 2 weeks

1
0
0 / 0

← Newer
1
2
3
Older →