We've got a couple different, identical, jboss-settings.xml files:

cct_module/jboss-maven/added/jboss-settings.xml
cct_module/os-java-s2i/added/s2i/jboss-settings.xml

That get configured by a couple different ways.

The first way is for s2i builds. And if you include the s2i modules, this is common.sh script is available to you during assembly:
cct_module/blob/master/s2i-common/common.sh
cct_module/blob/master/os-jws-s2i/added/s2i/assemble
cct_module/blob/master/os-java-s2i/added/s2i/assemble
cct_module/blob/master/os-eap-s2i/added/s2i/assemble
jboss-kie-modules/os.kieserver.s2i/added/s2i/assemble

The other way is for business central, decision central, and kieserver (in realtime decision server, intelligent process server, and bpmsuite business central and kieserver):

cct_module/os-eap-launch/added/launch/maven-repos.sh

The functionality of these two scripts, and anything else maven settings configuration-wise, should be combined into a single cct_module.

The reason not everything can move into the os-java-s2i module is that not all images (like business central or decision central) use s2i, and thus don't include that module.

And the maven-repos.sh script isn't really specific to eap, so shouldn't live in the os-eap-launch module.

As long as all places that need this functionality (either in s2i phase or launch phase) specify this module, then they will have access to the combined functionality.