Custom incoming mail handler - Tutorial for Atlassian Jira 8.5

[Chris]

Hello!

I am new to Atlassian SDK development and trying to create a custom incoming mail handler I followed the tutorial and tried to create it using a current Jira version (8.5) with the current SDK. However, I am not getting it to work. I found several discussion threads with different tips and tricks, but still having issues. If anybody could guide me in a "working direction" I would appreciate that very much.

In my pom.xml I am using the following versions:

<jira.version>8.5.0</jira.version>        
<jira.mail.version>10.0.0</jira.mail.version> <amps.version>8.0.2</amps.version> <plugin.testrunner.version>2.0.1</plugin.testrunner.version>
<atlassian.spring.scanner.version>2.1.10</atlassian.spring.scanner.version>

Therefore I have removed the @Scanned annotations in the classes.

The mail handler is showing up, but when trying to get to the next screens with the custom configuration, I am getting the following error: "The Jira server was contacted but has returned an error response.". In the log I see the following:

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'rocks.patch.plugins.jira.mailhandlerdefault.EditHandlerDetailsWebAction': Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'rocks.patch.plugins.jira.mailhandlerdefault.IssueKeyValidator' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}

Instead of publishing all code here I have decided to put it in a repository here:

https://github.com/patchrocks/mail-handler-default

This is probably now a very generic question, but I am not sure anymore where my issue exactly is (probably just a missing annotation or one too much) and which question I exactly could ask.

If there is anyhting in addition I can provide, please let me know. I appreciate any help. Thank you very much.

[Chris · Accepted solution]

Solved myself by not using dependency injection for own classes.