Last time I was trying was with EAP CR3 (just EAP part, no XP) and following artifacts were missing in the repo zips:

org.jboss.narayana:narayana-bom-test:7.1.2.Final-redhat-00001 (required from :wildfly-transactions)
software.amazon.awssdk:bom-internal:2.20.126.redhat-00001 (required from :wildfly-ee-feature-pack-galleon-shared)

(Note that the versions of those artifacts should not be hardcoded, but it should be versions of these components present in given CR.)

Full steps needed to build the sources were following:

• Update eap-maven-plugin in both the wildfly-core sources and EAP sources to the version of the plugin published in given release.
• Build wildfly-core sources first (nothing special needed).
• Build EAP sources:
  • Set wildfly-core version to the version that has been build in the previous step.
  • Align EAP sources according to the EAP manifest released in the CR & the XP manifest containing upstream versions of XP components or XP manifest produced of the same CR number:

     mvn -s ../settings.xml org.wildfly:wildfly-channel-maven-plugin:1.0.26:upgrade -DmanifestFile=../eap-manifest.yaml,../xp-initial-manifest.yaml -DinjectTransitiveDependencies=false -DdoNotDowngrade=false -DignoreStreams=org.apache.maven:*,org.apache.maven.resolver:*,org.codehaus.plexus:* -DignorePropertiesPrefixedWith=legacy. 

  • Build EAP:

     mvn install $MVN_FAST -Dmaven.repo.local=`pwd`/../local-repo -s ../settings.xml -U 

These steps somehow we will need to perform before releasing the final GA.