Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 5.2.0.Final
    • None
    • None
    • AMM Sprint 220
    • Hide
      * *Why we missed the bug?*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+


       * *What is required:*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+
      Show
      * *Why we missed the bug?*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+  * *What is required:*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+
    • ---
    • ---

    Description

      There are 3 Tag related CLI arguments

      --listTags

      --includeTags

      --excludeTags

      As I understand it Tags can be linked to rules and MTA should be able to apply those  --includeTags --excludeTags to refine which rules are selected for execution.

      The --listTags output is needs t be checked as cloud-readiness is listed but the tag in the openshift rules is actually just cloud

      The --excludeTags seems to work, so this command excluded some cloud-readiness rules from firing

      ./mta-cli --input ../samples/jee-example-app-1.0.0.ear --output $HOME/MTA_Output/jee_example_app_tags --target eap:7 --target cloud-readiness --excludeTags cloud

      However no MTA output is generated if the --includeTags parameter is used.

       

       

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated: