Description of problem:

The Weblogic rules in 129-weblogic-catchall.windup.yaml all have an effort set to 0, which means that even if the rule finds an issue, the issue will not show up in the generated report.

Version-Release number of selected component (if applicable): MTA 7.3.1

How reproducible: always

Steps to Reproduce:

1. Create a simple Java project with a source file that contains an import like import com.weblogic.foo.Bar;.
2. Replace the MTA 7.3.1 version of 129-weblogic-catchall.windup.yaml with the upstream 129-weblogic-catchall.windup.yaml version that fixes the pattern definitions for weblogic-catchall-01000.
3. Run MTA: ./mta-cli --log-level 100 analyze -s weblogic -t eap8 -i /path/to/java/project -o report --overwrite

Actual results:

The analysis.log contains the following line showing that weblogic-catchall-01000 found an issue:

level=unknown msg="finished rule" error=null found=1 rule=weblogic-catchall-01000 worker=4
level=info msg="rule returned" ruleID=weblogic-catchall-01000
level=unknown msg="rule matched" batch=violationRules ruleID=weblogic-catchall-01000

Details about the issue do show up in the output.yaml file.

However, since effort is set to 0, this issue will not show up in the generated static report.

Expected results:

Weblogic issues should appear in the generated static report.