The various testsuite/integration/microprofile-tck child modules contain a lot of common configuration. This increases in my ee-9 branch due to the need to execute those TCKs using the new wildfly-preview feature pack to provision.

Any example of this is all the TCK modules use the galleon-maven-plugin to provision a server, with the only real difference across the various modules being the layers that are provisioned. So the provisioning boilerplate can consolidated.

Try and consolidate these settings in the parent testsuite/integration/microprofile-tck/pom.xml.

A likely technique is to declare various plugin configurations in the top level 'build' config of the parent (making them available in all profiles) but for all executions set the 'goal' element to a maven property expression. Default value for the property being 'none', i.e. disabled. Then the various profiles in the child modules can set the properties to the normal goal for the executions, thus enabling them, plus extend the plugin configs with any non-common settings.