After upgrading a plugin from JIRA 6.2.8 to JIRA 7.2.7 I encountered a very strange error:
Failed to parse configuration class [...]; nested exception is
class path resource
cannot be opened because it does not exist
Did someone got such error before and if yes - how did you fix it?
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,
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.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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