wildfly-dev August 2025

wildfly-dev@lists.jboss.org

13 participants
37 discussions

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

1 month

7
16
0 / 0

[proposal] WildFly Maven Plugin, package bootable JAR for the cloud

by Jean Francois Denise

Hi, I’ve created a proposal[1] to package a WildFly Bootable JAR for the cloud when using the WildFly Maven Plugin (we are currently packaging a bootable JAR for bare-metal only). I’m looking for a feature team to work on this proposal. I would also need an outside perspective to fully form the team. Best regards, JF [1] https://github.com/wildfly/wildfly-proposals/pull/748

4 months

3
4
0 / 0

[proposal] Generate "javadoc-like" documentation for feature packs

by Jeff Mesnil

Hi, I’ve created a proposal[1] to generate a documentation archive when a feature pack is created (similar to the javadoc archive that is generated when a Java jar is built by Maven) I’m looking for a feature team to work on this proposal. Jean-Francois and Emmanuel already provided some PoC around this idea so I nominated you as SMEs :) But I’d need another outside perspective to fully form the team. This RFE does not impact the runtime so stability level is not directly applicable but I aim to do something equivalent to the quality expected by the “community” stability level. Best regards, Jeff [1] https://github.com/wildfly/wildfly-proposals/pull/739 -- Jeff Mesnil Engineer @ Red Hat http://jmesnil.net/

5 months, 1 week