plugin has an extra copy of atlassian-spring-scanner-annotation classes

Issue Summary

Plugin includes a dependency on atlassian-spring-scanner-annotation with scope compile. Under certain circumstances, the plugin causes Bamboo to fail to start up, as in: [Plugins failing to start due to 'plugin has an extra copy of atlassian-spring-scanner-annotation classes'|https://confluence.atlassian.com/confkb/plugins-failing-to-start-due-to-plugin-has-an-extra-copy-of-atlassian-spring-scanner-annotation-classes-959299076.html]

Steps to Reproduce

Install Bamboo Agents Usage Visibility Plugin v0.3

Install another plugin, such as [Build Status Tracker for Bamboo|https://marketplace.atlassian.com/apps/1212013/build-status-tracker-for-bamboo]

Stop Bamboo

Remove directories in <bamboo-home>/caches

Start Bamboo

Expected Results

Bamboo starts as expected

Actual Results

Bamboo fails to start, and the below exception is thrown in the {{atlassian-bamboo.log}} file:

2019-07-11 15:57:49,758 ERROR [ThreadPoolAsyncTaskExecutor::Thread 1] [OsgiPlugin] Unable to start the plugin container for plugin 'bamboo.web.resources.common'
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://18.0:0/META-INF/spring/spring-scanner.xml]; nested exception is java.lang.IllegalStateException: Cannot execute atlassian-spring-scanner-runtime: plugin has an extra copy of atlassian-spring-scanner-annotation classes, perhaps embedded inside the target plugin 'com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-web-resources'; embedding scanner-annotations is not supported since scanner version 2.0. Use 'mvn dependency:tree' and ensure the atlassian-spring-scanner-annotation dependency in your plugin has <scope>provided</scope>, not 'runtime' or 'compile', and you have NO dependency on atlassian-spring-scanner-runtime.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Issue Summary

Steps to Reproduce

Expected Results

Workaround

Comments (1)