Status: Verified (View Workflow)
Affects Version/s: None
Git Pull Request:https://github.com/jboss-openshift/cct_module/pull/273, https://github.com/jboss-container-images/jboss-datagrid-7-openshift-image/pull/87, https://github.com/jboss-container-images/jboss-jdv-modules/pull/6, https://github.com/jboss-container-images/jboss-datavirt-6-openshift-image/pull/60, https://github.com/jboss-container-images/redhat-openjdk-18-openshift-image/pull/32, https://github.com/jboss-container-images/jboss-kieserver-6-openshift-image/pull/48, https://github.com/jboss-container-images/jboss-kie-modules/pull/84, https://github.com/jboss-openshift/cct_module/pull/298, https://github.com/jboss-container-images/jboss-amq-6-openshift-image/pull/60
Sprint:CLOUD Maintenance Sprint 28
We've got a couple different, identical, jboss-settings.xml files:
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:
The other way is for business central, decision central, and kieserver (in realtime decision server, intelligent process server, and bpmsuite business central and kieserver):
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.