Running JIRA 6.4.12 with ScriptRunner 3.1.4 on my little test server. I'm making quite extensive use of scriptrunner of workflow conditions, validators and post-functions. Works great. My IT group decided to upgrade JIRA from 6.1 to 6.4.12 but they decided to go with version 184.108.40.206. The first problem, I'm running into is my workflow transitions with ScriptRunner based conditions are not visible so I'm assuming the conditions are failing. I check the log file and I see:
2016-04-05 14:32:47,595 http-bio-8443-exec-1 WARN 20022993 872x69734x1 yqdjn4 192.168.109.99 /browse/POCM-195 [com.atlassian.ozymandias.SafePluginPointAccess] A LinkageError indicates that plugin code was compiled with outdated versions. Unable to run plugin code because of 'java.lang.ClassFormatError - Illegal class name "com/onresolve/jira/groovy/canned/workflow/conditions/SimpleScriptedCondition/reporter-ValidatorOnlyCondition$run" in class file com/onresolve/jira/groovy/canned/workflow/conditions/SimpleScriptedCondition/reporter-ValidatorOnlyCondition$run'.
So is SimpleScriptedCondition no longer a valid class? Is there a replacement? Some documentation on how to migrate? Any other surprises for validators or post-functions or even behaviours and scripted fields?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs