While we wait for the impending release of the next version of JIRA Development Cookbook, here is something to cheer you up.
JIRA Development Cookbook eBook(s) are on SALE!
NoSuchBeanDefinitionException is a notorious exception in the JIRA Development world. Some even have had nightmares about it I hear!
But then, this is a well documented error and even we have attempted documenting it here - to save hours of debugging and, of course, to provide a good night's sleep!!
With the latest Atlassian Plugin SDK though, it seems the nightmares are back. And I have seen a rising number of questions about this error in Atlassian Answers and other forums. Are you one of those who ran into the same? If so, don't blame it on Atlassian or the plugin SDK. You are just ignorant, as I was for a good few hours, about the Atlassian Spring Scanner libraries.
Wow, it's been a while since the last post. Crazy schedule but this one is too cool to ignore!
Ever wondered how the nice little JIRA notification messages are created? The ones you get when an issue is created in JIRA?
Doing this is so easy that you will want to try it out in every new plugin that you write!
With the evolution of JIRA over the years, it has a set of nice APIs or helper methods for doing pretty much everything. But one thing that I always have to look up while developing plugins is using date and user pickers in a velocity template.
As usual, it is something that is really easy once you look it up. Here is a simplified version of what I have done in the last few versions of JIRA.
Ever since Plugins 2.0 was introduced, I have come across the NoSuchBeanDefinitionException more than anything else.
And this happens when you try to inject a JIRA component in the constructor. Following is a typical example.
We are pleased to announce that we are organizing a giveaway especially for you. All you need to do is just comment below the post and win a free copy of JIRA 5.x Development Cookbook.
Two lucky winners stand a chance to win copy of the book. Keep reading to find out how you can be one of the Lucky One.
I am sure most of you would know what a JIRA workflow is. And most of you would have custom workflows implemented in your JIRA instance - for good or bad!
And while maintaining those workflows you certainly would have used the JIRA workflow designer. Even people like me, who always likes to choose the "Text" view over "Diagram" view, has had to use it at some point. For example, while adding common transitions.