Uploaded image for project: 'WINDUPRULE - Red Hat Application Migration Toolkit rules'
  1. WINDUPRULE - Red Hat Application Migration Toolkit rules
  2. WINDUPRULE-164

Clean up and merge duplicate rules

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.6.0.Final
    • 2.5.0.Final
    • None
    • None

    Description

      From mzottner@ email:

      Clean-up and merge rules duplicates like:

      a)
      "WebSphere Web Application Binding" (websphere-xml-06000),
      "WebSphere Web Application Bindings" (websphere-xml-06000) and
      "WebSphere Web Binding" (ResolveWebSphereWebXmlRuleProvider_1)

      b)
      "JBoss web application descriptor (jboss-web.xml)" (jboss-eap5-xml-09000) and
      "JBoss Web XML" (ResolveJBossWebXmlRuleProvider_1)

      c)
      "JBoss 5.x EAR Descriptor" (jboss-eap5-xml-02000),
      "JBoss EAR Configuration " (jboss-eap5-xml-08000) and
      "JBoss application descriptor" (jboss-eap5-xml-19000) -> This rule should definitely be cleaned-up as it generates many entries.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WINDUP-1046 <has-hint> and <has-classification> is missing in the documentation.

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

          Bug - A problem that impairs or prevents the functions of the product. WINDUP-1057 Composite conditions (not, and, or) need to pass the name of the payload variable to its nested conditions

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

          Bug - A problem that impairs or prevents the functions of the product. WINDUP-1059 Support hasHint for File condition

          • 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
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. WINDUP-1041 Classifications without story points should not be counted as "incidents"

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New

          Task - Represents a small unit of work that is not end-user facing. WINDUP-1054 Docs: Add <iterable-filter> to docs //Tests: Support count check in <classification-exists> and <hint-exists>

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New

          Activity

            People

              ozizka_jira Ondrej Zizka (Inactive)
              dansmit Dan Smith (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: