Closed agoncal closed 1 year ago
I think this rule (and the Swing one too) should be reevaluated.
For these reasons, I believe rules that dictate that "if <javafx/swing/awt> therefore
I'd say we should ease the message here at the very least, make it informational only, and that the customer just needs to be aware of the API usage, but the message should not say "it does not work".
@brunoborges makes sense.
BTW I've worked on this rule because the AirSonic app that we bundle in CAT has a Swing front-end ;o)
@KaiqianYang as we discussed, I've refactored the existing Java FX rule that you've created. I got rid of the source (springboot) so it becomes generic to all Azure targets. And because the rule already existed in WindUp, I've moved it to
technology-usage
and override it. I've also reword the message.Let me know what you think.