Remaining UX issues in readme for microprofile-fault-tolerance QS ----------------------------------------------------------------- Key: WFLY-13670 URL: https://issues.redhat.com/browse/WFLY-13670 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 20.0.0.Final, 20.0.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor (1) WildFly pom is used instead of EAP XP one: {code} <groupId>org.wildfly.bom</groupId> <artifactId>wildfly-microprofile</artifactId> <version>${version.server.bom}</version> where ${version.server.bom} is the version of your JBoss EAP XP, in our case "1.0". {code} This is mentioned in JBEAP-19481 as well. (2) Unsupported commands for starting and managing EAP: {code} mvn wildfly:run & mvn wildfly:execute-commands -Dwildfly.commands=/extension=org.wildfly.extension.microprofile.fault-tolerance-smallrye:add mvn wildfly:execute-commands -Dwildfly.commands=/subsystem=microprofile-fault-tolerance-smallrye:add mvn wildfly:shutdown -Dwildfly.reload=true {code} (3) I think there's no need to add the subsystem if using standalone-microprofile.xml config where it is already present. (4) Consider adding standard sections - see other QS * Use of the EAP_HOME and QUICKSTART_HOME Variables * Start the JBoss EAP XP Standalone Server * Build and Deploy the Quickstart * Access the Application * Undeploy the Quickstart * Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse There might be additional issues I don't see because of JBEAP-19481.