Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-160

Improve Exception messages / handling

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • 2.0.0.CR1
    • 1.0.0.Alpha2
    • Base Implementation
    • None

    Description

      We should create an Exception message id for each exception Arquillian can throw to be able to identify them.

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users ARQ-395 Create a better exception message when no DeployableContainer is found in ConainerRegistry

          • 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

          Feature Request - Feature requests from customers and/or users ARQ-224 Create Wiki entries for every Error Message id

          • 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.
          • Open

          Activity

            People

              Unassigned Unassigned
              aslak@redhat.com Aslak Knutsen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: