-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Step four of the WFCORE-6611 'epic'.
Allow an external caller to set a property that tells the testuite to use the channels available in the reactor when provisioning.
If set, when configuring testsuite provisioning by the wildfly-maven-plugin (see WFCORE-6612), pass dynamically determine a set of channels to use and use the -Dwildfly.channels system property to pass those to the plugin execution.
This is similar to WFCORE-6614, but is meant for cases where the caller doesn't want to explicitly specify channels, it wants to use what's known to the build.
See https://docs.wildfly.org/wildfly-maven-plugin/releases/4.2/dev-mojo.html#channels for more re the -Dwildfly.channels system property.
- depends on
-
WFCORE-6612 Convert testsuite provisioning from galleon-maven-plugin to wildfly-maven-plugin
- Resolved
-
WFCORE-6613 Create channel and manifest artifacts for the core feature pack
- Resolved
- is cloned by
-
WFLY-18793 Dynamic configuration of channels to use when testing
- Closed
- is depended on by
-
WFCORE-6616 Add per PR or nightly test jobs to test channel based provisioning
- Open
- is incorporated by
-
WFCORE-6611 Introduce channel based provisioning into the testsuite
- Open