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

Inconsistent results with SB2Quarkus catch all rules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 5.3.0.Final
    • Quarkus
    • None
    • AMM Sprint 221
    • None

      There are some Spring catch all rules (springboot-generic-catchall-00100) that are triggered when a Spring artifact is identified providing there isn't already a hint for that artifact.
      However we also have numerous rules (e.g. Rule Id embedded-framework-90000) that generate technology tags. Those rules create Information hints against the same artifacts. They both execute within the
      PostMigrationRulesPhase

      There is an <executeAfter> predicate that can be attached to rules (guide).

      Let's try to orchestrate the rules execution order so the spring-generic-catchall-* rules always execute before the technology identification rules.

              pcattana Philip Cattanach
              pcattana Philip Cattanach
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: