ClassCastException when executing automation rules with both A4J and A4J Lite installed

Issue Summary

java.lang.ClassCastException errors can occur if A4J and A4J lite are both installed on the same server while A4J Lite is disabled

Steps to Reproduce

1. Install A4J lite
2. Install 'Xporter for Jira app' or 'ScriptRunner' (this bug is not caused by the presence of either of these apps, but they do help to illustrate the issue here).
3. Install A4J (this will automatically disable A4J lite)
4. Try to execute any automation rule in A4J on a Service Desk project

Expected Results

Rule should be executed without errors even with either of the A4J disabled.

Actual Results

Rules fail with the following exception thrown in the atlassian-jira.log file:

java.lang.ClassCastException: com.xpandit.jiraxporter.integration.automationforjira.XporterActionIntegration cannot be cast to com.codebarrel.automation.api.thirdparty.AutomationRuleComponent

java.lang.ClassCastException: com.onresolve.scriptrunner.automation.ExecuteScriptIssueActionV2 cannot be cast to com.codebarrel.automation.api.thirdparty.AutomationRuleComponent

Workaround

Uninstall either A4J or A4J Lite

Note

• If you don't initially replicate this issue, restart Jira and the issue should then be reproducible
• We have not been able to reproduce this issue without Xporter for Jira or ScriptRunner installed
• We have also only been able to reproduce this on Service Desk projects