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 http://blog.polarion.com/wp-content/uploads/2013/07/Handout_SVN_Webclient_Installation.pdf
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?
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:
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 :)
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:
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG