Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-30051

Server is provisioned when following QS README instructions using externally provided server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • 8.1.0.Beta
    • Quickstarts
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      When following the default (first) scenario for 8.1 Beta quickstarts, which is

      1. get server zip, unzip and start it
      2. build quickstart "mvn clean package"
      3. .. the rest, not relevant now

      The second step is executing eap-maven-package goal present in activeByDefault profile "provisioned-server" which means it builds the application deployment, provision the server and deploy it to it. This makes no sense as the instructions says to provide external server instance to deploy to in next step.

      While it works (we can still deploy the app to the already started server after second step), it is doing unnecessary work, at very least it takes needlessly more time to finish the default workflow.

      Since the README also contains separate instructions for workflow with provisioned server, we should make the instructions (or profiles in QS) better.

              Unassigned Unassigned
              jbliznak@redhat.com Jan Blizňák
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: