Unable to Remove or Upgrade Subversion Plugin

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

After following the default uninstall procedure and removing all JARs, configuration files and restarting JIRA, you notice that the Subversion Plugin shows up in the System Information and you are also unable to install it again:

1 2 3 4 5 6 7 8 ___ User Plugins ____________________________ Number : 1 JIRA Subversion plugin : com.atlassian.jira.plugin.ext.subversion Version : 0.10.11.1 Status : disabled Vendor : Atlassian Pty Ltd Description : A plugin to integrate JIRA with Subversion.

The following error may also be observed in atlassian-jira.log after attempting to install or upgrade a more recently release version of the Subversion plugin.

1 2 2015-06-26 10:03:06,971 ajp-bio-38790-exec-640 ERROR user 603x431632x1 user 10.3.2.10 /secure/ViewSubversionRepositories.jspa [jira.config.webwork.JiraActionFactory] Error autowiring Action 'com.atlassian.jira.plugin.ext.subversion.action.ViewSubversionRepositoriesAction'. org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.atlassian.jira.plugin.ext.subversion.action.ViewSubversionRepositoriesAction': Unsatisfied dependency expressed through constructor argument with index 0 of type [com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager]: : No unique bean of type [com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager] is defined: Unsatisfied dependency of type [interface com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager]: expected at least 1 matching bean; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager] is defined: Unsatisfied dependency of type [interface com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager]: expected at least 1 matching bean

Cause

There might be JARs related to the Subversion plugin in the lib directory that is used by Tomcat. Check inside JIRA-INSTALL/lib:

  • atlassian-jira-subversion-plugin-#.#.#.jar

  • svnkit-#.#.#.jar

  • trilead-ssh2-build213-svnkit-#.#-patch.jar

Resolution

Follow the steps below and after that you will notice that there's no more mention to the Subversion Plugin in the System Information and you will be able to upgrade / install it again:

  • Stop JIRA.

  • Remove the files from your JIRA-INSTALL/WEB-INF/lib.

  • Start JIRA again.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.