Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2768

[EAP][XA] merge jta-crash-rec-eap quickstarts and update README

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • None
    • None
    • EAP6, EAP7
    • None

    Description

      Currently there are two jta crashrec quickstarts at https://github.com/jboss-openshift/openshift-quickstarts - `jta-crash-rec-eap6` and `jta-crash-rec-eap7`. Both code bases are mostly the same and the only real difference is existence of the template json, one for EAP6 and one for EAP7. As there is the code duplication and two quickstarts named in the same way are confusing they should be merged under one directory serving any EAP version.

      On top of that there should be updated README.md as it does not talk about specifics of the recovery on OpenShift.

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2795 [EAP][XA] jta-crash-rec-eap quickstarts needs to use proper messaging and database datasource

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2760 [EAP][XA] jta-crash-rec-eap7 quickstart doesn't work with sprint-21 img

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2938 [EAP][XA] jta-crash-rec-eap quickstarts should use correct settings with remote AMQ7 broker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kwills@redhat.com Ken Wills
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Pavel Drobek Pavel Drobek
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: