nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FileNotFoundException: JiraActionSupport.class cannot be opened because it does not exist

Suppie

Hello,

After upgrading a plugin from JIRA 6.2.8 to JIRA 7.2.7 I encountered a very strange error:

org.springframework.beans.factory.BeanDefinitionStoreException: 
Failed to parse configuration class [...]; nested exception is 
java.io.FileNotFoundException: 
class path resource 
[com/atlassian/jira/action/JiraActionSupport.class] 
cannot be opened because it does not exist

Did someone got such error before and if yes - how did you fix it?

Accepted answers

All comments

Lars Olav Velle

I think you are better off contacting the vendor of that particular add-on.

-Lars

Suppie

Unfortunately, I am the developer.

Lars Olav Velle

Ah!

Perhaps a better place to ask is:

https://community.developer.atlassian.com

-Lars

Suppie

Oh. Thanks...

unknown

I had the same error as you in another plugin that provided some custom fields. The error was gone as soon as I removed the annotations from Atlassian spring scanner from every class that provided a custom field. In fact,

ProjectImportableCustomField.class

is an interface implemented by the classes used for making custom fields. Maybe this helps you as well. The thing that really baffles me and freaks me out is that we have to remove those annotations from the custom field classes. The annotations from Atlassian spring scanner are supposed to be necessary. Why do we have to remove them?

Since your case seems to be related to other sort of classes, maybe web actions or controllers, perhaps you have to remove the annotations from those classes.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-development

jira-core