Description
I wrote a task module for Bamboo that takes an Atlassian Plugin jar built by Bamboo and installs it in a remote Confluence or JIRA instance (using UPM) - https://plugins.atlassian.com/plugin/details/602870
The task requires that the parent job must have an artifact dependency from an earlier stage that points to the plugin jar that is to be installed into the remote instance.
The configuration screen for the task allows the user to select the desired artifact from the list of artifact dependencies.
Since upgrading my plugin to be a plugins-2 plugin, the config screen is no longer able to be loaded. Bamboo generates the inner exception:
[INFO] [talledLocalContainer] Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.atlassian.bamboo.plugins.confdeploy.AutoDeployConfigurator': Unsatisfied dependency expressed through constructor argument with index 1 of type [com.atlassian.bamboo.plan.artifact.ArtifactSubscriptionManager]: No unique bean of type [com.atlassian.bamboo.plan.artifact.ArtifactSubscriptionManager] is defined: expected at least 1 matching bean
It would be great if the ArtifactSubscriptionManager bean was accessible to plugins, or an alternative means for selecting an artifact was provided.