How to install svnwebclient for jira subversion plugin?


We are evaluating both the jira subversion plugin[Atlassian Owned] and the subversion ALM plugin[Kinto Soft Owned]. In subversion ALM plugin web client is the inbuilt feature. But for jira subversion plugin its not. I have gone through the following pdf for installation of svn web client

But i am not succeeded with that . Can any one help in this

Steps i followed for the installation

Step1: Downloaded the svnwebclient war file

step2: Deployed the war file using Apache [on jira installed machine ]

step3: changes made in web.xml file

Not sure which url i have to give after selecting web link for View Format,Changeset Format,File Added Format,File Modified Format,File Replaced Format,File Deleted Format

Whether these svnwebclient is necessary ? or i can simply i can add the repository to jira subversion plugin and configure the URLS pointing to the repository?

1 answer

1 accepted

0 votes
Accepted answer

Thank you for your interest in the Subversion ALM plugin and also by bringing an interesting comparative about two plugins....

Even I might understand people want to compare both solutions:

ALM plugin vs (Atlassian's plugin + 3rd party Subversion web client)

it is not really a comparative about two solutions. It is a comparative about two vendors:

Atlassian VS 3rd party small vendor

ALM is so clearly superior to the Atlassian's plugin that there are not any reason to use the Atlassian's plugin. Briefly: ALM was born as a fork of the Atlassian plugin so almost the 100% of features provided by the Atlassian's plugin are also supported by ALM, it means you can do nothing with the Atlassian's plugin that you could not do them with the ALM plugin too. While the opposite is not true: the ALM plugin brings a lot of features not supported by the Atlassian's plugin. So, there is not any benefit in using the Atlassian's plugin.

So, why are companies still using the Atlassian's one? This is a mistery. The only one reason is due the vendor behind each solution or simply they did not realize there was a better alternative.

The only one feature supported by the Atlassian's plugin and not by the ALM plugin is that you can configure any 3rd party web client for Subversion (ViewVC, FishEye, Polarion, etc.). While you cannot do it with the ALM plugin as it brings with a CUSTOMIZED version of Polarion. But there are good and powerful reasons for this...

In your particular case, using Polarion as independent server to browse on Subversion has not too much sense because:

  • it would require you maintain a secondary server (Tomcat) so it would increase your adminsitration costs/effort (you have to register every Subversion repository twice, once on the Atlassian's plugin and once on Polarion itself in order to keep them synchronized and you would also have to configure some urls as you have discovered now). All this stuff is done by the ALM plugin automatically.
  • Polarion supports ssh+svn access protocol well, while the Atlassian's plugin not. So if you need to use such protocol you couldn't. However, the ALM plugin extended the ssh+svn support from Polarion to the Atlassian's plugin.
  • With the ALM plugin, you can also use Polarion as Standalone Web Client for Subversion, it means you can access directly to the Polarion browser ignoring JIRA just like it was installed on Tomcat directly. Therefore, with the ALM plugin developers can use Polarion without requiring a JIRA user account. There is an option for that, so you could also require that everybody using Polarion must be logged in JIRA first.
  • The Subversion Web Client is used by Polarion inside its products, but as Standalone web client it has been discontinued, so you would use an unsupported product in production.
  • The Polarion's browser has been customized and improved a lot by the ALM plugin. Some examples: it has a GUI for configuration rather than requiring to modify the web.xml file. The discontinued library used by Polarion to highlight sources has been fully replaced by a well maintained alternative which highlights much more languages. Commits graphs (displaying JIRA issues) and commits calendars are provided by the ALM plugin only. The JIRA issues are recognized and highlighted by the ALM plugin on Polarion while browsing, etc.
  • The ALM plugin supports JQL for Subversion which is a critical feature for traceabilty.
  • The ALM plugin is integrated with Agile so you can see commits on Scrum and Kanban boards.
  • The ALM plugin is better maintained, so you can get fixes for bugs or get new features implemented within few days.
  • And there are much more features are in the ALM plugin's roadmap, like support for tracking merges, comparing Office and PDF document versions, etc.


Many thanks for the detailed explanation.

I have only 1 question. Please answer because i just want to know.

In polarian svnwebclient installation guide they explained deploy the war file on tomcat server and modify web.xml. In this case my question is

1. we need to deploy this war file on svn server or on jira instance because our jira instance is in one server and the svn server is different.



No matter JIRA or Subversion Server as svnwebclient requires its own Tomcat instance in order to run, so you may deploy it one the same host than JIRA or SVN Server or even a new 3rd party host.

In the particular case of Subversion ALM, there were not too much alternatives, the Polarion's svnwebclient must run on the same Tomcat (Java App Server) instance than JIRA. Otherwise, it would be impossible. But as standalone WAR app... you can install it anywhere :)


Many Thanks

Is it possible to use the subversion ALM only for browsing the change committed for the issue and disable its use as Standalone Web Client for Subversion.



disable its use as Standalone Web Client for Subversion.

Do you mean disable the Subversion/Browse entry at the JIRA top menu? Yes.

Yes on top Subversion --> SVN Web Client menu

Please go to the Manage add-ons section (Administration > Add-ons > Manage add-ons) from your JIRA instance,

Locate the Subversion ALM entry in the plugins list from the UPM and click on it to expand.

Then click on the 112 of 112 modules enabled link in order to list all the modules provided by the plugin and installed on JIRA:

The entries below would disable:

  • the full Subversion top menu:
Subversion Top Menu Section


  • The SVN Web client only:
SVN Web Client


  • or the link to create issue commit calendars based on saved filters:
SVN Filter Report



Many thanks for the answer + good plugin :-)



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,019 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you