Valiantys base plugin exception

Lukáš Maruniak October 20, 2014

Hi, 

Recently, we've upgraded JIRA to version 6.3.7.

However, when we want to use functionality from Valiantys base plugin - Link a new issue - we got 404 error response and this exception in log: 

 

2014-10-20 15:24:12,802 http-bio-8381-exec-1559 ERROR jira-admin-connector 924x1143148x5 17zhqui 10.6.134.66,127.0.0.1 /secure/CreateIssueAndLink.jspa [jira.config.webwork.JiraActionFactory] Error autowiring Action 'com.valiantys.jira.plugins.exocet.webwork.CreateIssueAndLinkDetailsAction'.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.valiantys.jira.plugins.exocet.webwork.CreateIssueAndLinkDetailsAction': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.valiantys.jira.plugins.exocet.webwork.CreateIssueAndLinkDetailsAction]: Constructor threw exception; nested exception is java.lang.NoSuchMethodError: com.atlassian.jira.web.action.issue.CreateIssueDetails.<init>(Lcom/atlassian/jira/issue/IssueFactory;Lcom/atlassian/jira/web/action/issue/IssueCreationHelperBean;Lcom/atlassian/jira/bc/issue/IssueService;)V
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)

 

Is there a way, how to solve this ?

 

Regards, 

Lukas

1 answer

0 votes
crf
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 20, 2014

This is a binary incompatibility caused by the plugin extending an action that is in jira-core.  There are no API stability guarantees for jira-core classes.

Valiantys will need to release a new version of their plugin to fix this.

crf
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 20, 2014

For the curious, the action's constructor was changed as part of fixing https://jira.atlassian.com/browse/JRA-34926 and though you did not specify the old version you were upgrading *from*, my guess is that it must have been pre-6.3.

Suggest an answer

Log in or Sign up to answer