Currently /home/jboss/.m2/settings.xml is a fixed maven config.

It includes maven central repositories and red hat repositories using a java property activation (com.redhat.xpaas.repo.jbossorg, com.redhat.xpaas.repo.redhatga).

When users wants to include their own settings on maven, they need to keep this settings (which is somehow internal to Red hat) with their settings.

known usecases are:

• Include custom repositories (nexus)
• configure proxy. Even if there's a proxy configured for whole openshift, maven needs to be setup with proxy. In case HTTP_PROXY and HTTPS_PROXY are set, this might be automatically setup on settings.xml. See there's a NO_PROXY for 172.10.* and 10.1.* that should be setup too (again internal to Red hat implementation)

Right now solution needs to modify kieconfigs-7.x.x configmap to add:

• create a config map with settings.xml that honors internals of Red hat + customizations by user.
• Add volume and volume mount to have that file on pod
• Add env MAVEN_CUSTOM_SETTNGS to use that file instead of /home/jboss/.m2/settings.xml

• Repeat all that config for servers (configuration for kie-server)

In case user update the operator, repeat all the operation for new config map kieconfigs-7.x.x

• Is it possible to add an option to use a config map to override default settings.xml?
• Can the customizations from customer be mixed with the internals of red hat so we don't have to deal with obsolete config if properties are added or modified? The file to follow would be standalone-openshift.xml which is customizable too.