Description of problem:

In MTA 7.0.0 - the XML custom rule files are converted to the new YAML format during analysis.
The issue occurs when using javax-package-custom-target.windup.xml as a custom rules file - it doesn't get triggered after conversion

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

mta-operator-bundle-container-7.0.0-52

How reproducible:

100%

Steps to Reproduce:

Analyze tackle-test app with the following analysis configuration:

• Source code
• Skip "Set targets"
• Application and internal dependencies only
• Upload this rules file manually or from a repository:  javax-package-custom-target.windup.xml
• No additional advanced options

Actual results:

javax-package-custom-target-00001 (ruleID) wasn't triggered and no related migration issue was found

Workaround:

Modify the condition within the rules xml file to be like this:

<when>
    <javaclass references="javax{*}">
        <location>package</location>
    </javaclass>
</when>