The testsuite/galleon tests are testing updating all 3 feature packs (wildfly-ee, wildfly, wildfly-preview) as part of a single maven plugin execution.

This needs to be broken up so we can properly limit what gets tested based on what a particular overall test job is intended to test. For example, a test job that isn't testing wildfly-preview in general should not be testing the wildfly-preview feature pack in testsuite/galleon. A test run that assumes none of the expansion modules are built should not be testing the wildfly feature pack.

The wildfly-preview aspect is critical. Tests of wildfly-preview will not work in an SE 11 environment but the current test design tries to do so. It's only because of the mistake I made that WFLY-19332 attempts to correct that we didn't notice this during the early stages of WF 32 work.