There's something strange - to me - going on with spring scanner 1.2.6 with the JIRA 7.X series. From spring scanner's documentation, I see that they are upgrading to version 2.0 to use with JIRA 7.2.
At any rate, here is what to do: do not rely on constructor based injection. I don't know why. Instead, use property injection. So for example, adapt the custom field tutorial to be as follows (updated code to remove deprecation warnings):
import com.atlassian.plugin.spring.scanner.annotation.component.Scanned;
import com.atlassian.plugin.spring.scanner.annotation.imports.ComponentImport;
@Scanned
public class IntegerCFType extends GenericTextCFType
{
private static final Logger log = LoggerFactory.getLogger(IntegerCFType.class);
@ComponentImport private final CustomFieldValuePersister customFieldValuePersister;
@ComponentImport private final GenericConfigManager genericConfigManager;
@ComponentImport private final TextFieldCharacterLengthValidator textFieldCharacterLengthValidator;
@ComponentImport private final JiraAuthenticationContext jiraAuthenticationContext;
public IntegerCFType(CustomFieldValuePersister customFieldValuePersister, GenericConfigManager genericConfigManager,
TextFieldCharacterLengthValidator textFieldCharacterLengthValidator, JiraAuthenticationContext jiraAuthenticationContext)
{
super(customFieldValuePersister, genericConfigManager, textFieldCharacterLengthValidator, jiraAuthenticationContext);
this.customFieldValuePersister = customFieldValuePersister;
this.genericConfigManager = genericConfigManager;
this.textFieldCharacterLengthValidator = textFieldCharacterLengthValidator;
this.jiraAuthenticationContext = jiraAuthenticationContext;
}You should not need to add anything to atlassian-plugin.xml with this approach; we are using annotations instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.