[wildfly-dev] Bom builder thoughts

Some thoughts related to our 'bom builder' modules, sparked by the fact they are causing issues with syncing WildFly content from JBoss Nexus to Maven Central. 1) The configuration of the plugin that generates the bom includes elements like 'parent' and 'license' that also appear in the root level of a pom. This has led to trouble, so I suggest renaming these elements. https://issues.redhat.com/browse/NEXUS-967 was a problem where some tooling on JBoss Nexus was confused by these and was unwilling to sync content to Central because of the presence of these artifacts. This is now fixed. But, now we see Central is rejecting these poms. Exactly why is still unclear but a theory is that they are looking at the plugin configuration section, confusing them for document roots, and rejecting the pom because the 'document root' is missing required elements. I'll probably file an issue to rename these config elements. 2) Full WF uses `wildfly-bom-builder-plugin` for bom generation, while core has a 'component-matrix-builder' module that uses a `wildfly-component-matrix-plugin`. These look very similar. Can't we just use `wildfly-bom-builder-plugin` in core? Both plugins have a similar config that has the issues discussed in #1. 3) AFAICT output of Core's component-matrix-builder module isn't used anywhere, nor do we do anything to maintain it. One substantive commit since 2019. We should either: a) Drop this, or b) Use it in WF as the 'core-bom' instead of using wildfly-core-parent. I filed https://issues.redhat.com/browse/WFLY-20833 to explore the latter idea. Best regards, -- Brian Stansberry Architect, JBoss EAP WildFly Project Lead He/Him/His