[jboss-jira] [JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

[Radoslav Husar (Jira)]

     [ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated WFLY-13670:
----------------------------------
    Description: 
The 2 issues remaining are:

(5) Prerequisites and System Requirements sections both mention JDK and Maven versions. While JDK is just a duplicate, Maven version does not match in two sections. If the Maven version in standard System Requirements section is too old we should consider updating it.

(6) Build and Deploy the Quickstart section says "Make sure you start the JBoss EAP XP server as described above." and points to Start the JBoss EAP XP Standalone Server but this section is not above but below.
Suggestion: move Start the JBoss EAP XP Standalone Server above Build and Deploy the Quickstart and then you can point to this section from Creating the Maven Project from sentence "Start a JBoss EAP XP instance using the microprofile server profile."

  was:
(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.



> 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
>
> The 2 issues remaining are:
> (5) Prerequisites and System Requirements sections both mention JDK and Maven versions. While JDK is just a duplicate, Maven version does not match in two sections. If the Maven version in standard System Requirements section is too old we should consider updating it.
> (6) Build and Deploy the Quickstart section says "Make sure you start the JBoss EAP XP server as described above." and points to Start the JBoss EAP XP Standalone Server but this section is not above but below.
> Suggestion: move Start the JBoss EAP XP Standalone Server above Build and Deploy the Quickstart and then you can point to this section from Creating the Maven Project from sentence "Start a JBoss EAP XP instance using the microprofile server profile."



--
This message was sent by Atlassian Jira
(v7.13.8#713008)