Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: None
Affects Version/s: None
Component/s: MTA CLI
Labels:
None

Blocked:
False
Ready:
False
RCA Description:

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:_+
[QE] How to address?:
---
[QE] Why QE missed?:
---
Market:

Sprint:
Sprint 215 AMM, Sprint 217 AMM

Regression:
None

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

The attached custom rule when executed against that attached java class has inconsistent results when executed on Java 8 compared to Java 11.

When executed by the 5.2.1.Final version of the CLI using Java 8 both custom rules fired as expected.

When executed by the 5.3.0-SNAPSHOT version of the CLI using Java 11 the rule that identifies the java.awt.Font.getPeer() method fails to fire.

The command I used to execute the rule and generate the attached MTA Source Code Report screenshots was:

./mta-cli --input $HOME/temp --sourceMode --userRulesDirectory $HOME/CustomRules/java-internals-custom.windup.xml --output $HOME/MTA_Output/OpenJDK11internals --target cloud-readiness

java-internals-custom.windup.xmlFontGetPeer.java