Change server startup documentation to reference local installation and standalone-microprofile.xml --------------------------------------------------------------------------------------------------- Key: WFLY-13464 URL: https://issues.redhat.com/browse/WFLY-13464 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 19.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker The QS is included in EAP XP 1.0.0.GA-CR1 Quickstarts ZIP, but its instructions are WildFly specific. (1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc. (2) Starting the server with unsupported method "mvn wildfly:run &". Please use standard section {{Start the JBoss EAP Standalone Server}} or use a similar steps to start the server. The same applies for {{mvn wildfly:execute-commands}}, {{mvn wildfly:shutdown -Dwildfly.reload=true}} and {{mvn wildfly:shutdown}} commands. (3) When trying the WF commands with EAP XP1 server, they fail: {code} [nziakova@laptop microprofile-openapi]$ export JBOSS_HOME [nziakova@laptop microprofile-openapi]$ mvn wildfly:run & ... [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run (default-cli) on project microprofile-openapi-quickstart: Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run failed: Failure to find org.wildfly:wildfly-dist:zip:7.3.1.GA-redhat-SNAPSHOT {code} (4) When trying standard server start, the QS works fine without the step {{Add support for MicroProfile OpenAPI by adding the requisite extension and subsystem.}} - is it needed for EAP? {code} EAP_HOME/bin/standalone.sh -c standalone-microprofile.xml {code}