Introduced by WFLY-19871 (https://github.com/wildfly/wildfly/pull/18316), WildFly build now use data from manifest files during build of user BOMs (eg. org.wildfly.channels:wildfly-ee manifest is used for building of org.wildfly:wildfly-ejb-client-bom)

But the current implementation is not working out of the box, the usage of the manifest is declared in versionless manner for the BOM builder plugin:

                            <channels>
                                <channel>
                                    <manifest>
                                        <groupId>org.wildfly.channels</groupId>
                                        <artifactId>wildfly-ee</artifactId>
                                    </manifest>
                                </channel>
                            </channels>

and contrary to expectations this won't resolve to the org.wildfly.channels:wildfly-ee version from this WildFly build, but it resolves other version, from public repositories (34.0.0.Final ATM of writing this)

The result is then that generated BOMs don't use expected versions corresponding to the WF revision we are trying to build.