| Name | JIRA Subversion Plugin |
|---|---|
| Vendor | Atlassian Pty Ltd (Website) |
| Authors | Mike Cannon-Brookes, Dylan Etkin |
| Homepage | http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin |
| Issue Management | http://jira.atlassian.com/browse/SVN |
| Categories | Remote Access |
| Version | 0.10.3 |
| Availability | JIRA v3.12 to v3.12.3 |
| State | Stable |
| Support |
|
| License | Freeware / Open Source (BSD) |
| Price | Free |
| Release Docs | http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin |
| Java API Docs | n/a |
| Download Source | http://svn.atlassian.com/svn/public/contrib/jira/subversion-jira-plugin/tags/subversion_jira_plugin_0_10_3/ |
| Download JAR | atlassian-jira-subversion-plugin-0.10.3.zip |
Compatibility With JIRA
| Plugin Version | 3.2.x | 3.3.x | 3.4.x | 3.5.x | 3.6 | 3.7-beta2 | 3.7.x | 3.8.x | 3.9 | 3.10 | 3.11 | 3.12.2 | Tested | Supported |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0.6.1 |  |
|||||||||||||
| 0.7.1 | |
|||||||||||||
| 0.8.2 | |
|||||||||||||
| 0.9.1 | |
|||||||||||||
| 0.9.2 | |
|||||||||||||
| 0.9.3 | |
|||||||||||||
| 0.9.4 | |
|||||||||||||
| 0.9.5 | |
|||||||||||||
| 0.9.6 | |
|||||||||||||
| 0.9.7 | |
|||||||||||||
| 0.9.8 | |
|||||||||||||
| 0.9.9 | |
|||||||||||||
| 0.9.11 | |
|
||||||||||||
| 0.9.12 | |
|||||||||||||
| 0.10.0 |  |
|
Daniel Petzen (Feb/29/2008) | |||||||||||
| 0.10.1 | |
|
|
David Chui (Jan/29/2008) | ||||||||||
| 0.10.2 | |
|
|
David Chui (Mar/25/2008) | ||||||||||
| 0.10.3 | |
|
|
David Chui (Apr/03/2008) |
Overview
A plugin to integrate JIRA with Subversion.This plugin displays Subversion commit info in a tab on the associated JIRA issue. To link a commit to a JIRA issue, the commit's text must contain the issue key (eg. "This commit fixes TST-123").
Features
- Support multiple subversion repositories
- Supports http, https and svn protocols. Please note, the plugin currently does not support svn+ssh protocol (public/private key authentication) (SVN-145).
- Displays the Subversion revisions made against any JIRA issue, along with the changed paths
- Links revisions, file changes and diffs directly to ViewCVS for web based SVN viewing
- Subversion Commits Report displays recent commits mentioning JIRA issues for a project. Eg. see Apache Geronimo commits mentioning JIRA issues
Screenshots
|
Screenshots (view as slideshow) |
||||||
|---|---|---|---|---|---|---|
|
|
|
||||
|
|
|
||||
| Screenshot of the plugin in action. | pic | |||||
|
||||||
Notes
By default, the subversion index will refresh every 1 hour, this means that you may not see your changes in Jira immediately. You can edit how often the service runs by editing the delay from Administration -> System -> Services.
Special thanks to the TMate JavaSVN library - it has made the development of this plugin a lot easier
Install Instructions
(further notes in the readme.txt inside the download)
1. Copy files
- Copy the following jar files from the distribution's lib/ directory into JIRA's WEB-INF/lib. If you are upgrading the plugin, make sure you delete the old ones from WEB-INF/lib first.
- atlassian-subversion-plugin-*.jar
- javasvn-*.jar (if any)
- svnkit-*.jar (if any)
- ganymed-*.jar (if any)
- trilead-*.jar (if any)
- Copy subversion-jira-plugin.properties into JIRA's WEB-INF/classes.
To clarify the file locations:
- If you are using JIRA Standalone, copy the jar files into atlassian-jira/WEB-INF/lib and the .properties file into atlassian-jira/WEB-INF/classes.
- If you are using the WAR distribution, create the directory edit-webapp/WEB-INF/lib and copy the jar files into it. Then copy the .properties file into edit-webapp/WEB-INF/classes and rebuild and redeploy the JIRA war file.
2. Test plugin against svn.atlassian.com (optional)
Out the box, subversion-jira-plugin.properties is configured to display commits from a sample repository. To test that the plugin works:
- Create a test project with key TST in your JIRA installation, and create 3 new issues under this project (TST-1, TST-2, TST-3). Grant your current user the View Version Control permission.
- Restart JIRA
- Visit TST-1. You should see a "Subversion Commits" tab containing commits:
- Visit TST-3. You should see commits under it's "Subversion Commits" tab too:
If TST-3 shows no commits.. but you did see commits for TST-1, then you probably haven't fixed the jira.option.ignore.url.with.key property mentioned above. Change the property, then delete the $INDEXDIR/plugins/atlassian-subversion-revisions directory to cause JIRA to refetch and reparse the commits, and restart JIRA.
3. Subversion Configuration
In version 0.10.0, we've added a configuration interface in the Administration section. This obviates the need to configure your repositories in WEB-INF/classes/subversion-jira-plugin.properties. But if you already have them configured there, there's no need to make any changes. The plugin will read your configuration and store it internally. From that point on you should use the web interface to make changes or add/remove repositories as the properties file will not be read again. Please note though if you are using the subversion-jira-plugin.properties{} file and want to add/edit a repository, you should either make the changes to the properties file or start Jira without the property file and add your repositories through the web interface. (See SVN-180)
To add repositories, go to the Administration section and select "Subversion Repositories" from the sidebar and then select "Add". Next enter the repository's information to the form. If you you have a svn web interface (ViewVC, Fisheye, etc) you can also configure the 'linkformat' properties to link to it. The interface will pre-populate ViewVC, Fisheye, and WebClient for SVN links for you, but you may need to edit them depending on the repository's setup:
When you've finished click "add". There will be a delay before Jira returns to the repository list while the new repository is indexed. When the indexing is finished, the list will be displayed:
Repositories can also be editing or deleted from this list.
Upgrade Instructions
Upgrading the plugin (typically done as part of a JIRA upgrade) follows the same process as installing. There is one important extra step - delete the Subversion plugin's index files on disk before you start the new JIRA.
The Subversion plugin creates a search index of Subversion commits in below the JIRA index directory, in plugins/atlassian-subversion-revisions/. The new version of the Subversion plugin may not use the same indexing format, and the plugin cannot (yet - see SVN-173) detect this. If you start a new plugin with an old index, you may get strange errors.
Troubleshooting Instructions
Experiencing a problem with the plugin?
- Go to Administration -> Plugins, and ensure that there is a "Subversion Plugin" with the expected plugin version. If the version is wrong you might have two atlassian-jira-subversion-plugin-*.jar files in WEB-INF/lib.
- If the plugin isn't listed, it wasn't added properly or failed to load. Check the JIRA logs for Subversion-related errors. The log location depends on how JIRA is installed - see Where are the JIRA logs?
If the plugin loads, but you don't see commits:
- Check that the current user has the View Version Control permission.
- Have you made any Subversion commits mentioning JIRA issue keys? If not, obviously you won't see any links in JIRA.
- If in doubt of your configuration, try deleting the Subversion plugin's index on disk. This is the plugins/atlassian-subversion-revisions directory found under the index directory (check Administration -> Indexing for this). Then restart JIRA. Watch the logs for any errors.
- To eliminate network problems (firewalls, etc), try connecting to svn.atlassian.com.
- Finally, to see everything the Subversion plugin does (on startup), edit JIRA's log4j.properties, and add the lines:
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console, filelog log4j.additivity.com.atlassian.jira.plugin.ext.subversion = false
- Double-check that you have set jira.option.ignore.url.with.key=false in jira-application.properties.
If you make any configuration changes, please delete the $INDEXDIR/plugins/atlassian-subversion-revisions directory and restart JIRA to make the change take effect.
Support / Bug Reports / Feature Suggestions
If you have an installation problem or a question please check the debugging checklist above and create a support requestif that doesn't help. If you have found a bug or would like to raise a new feature request please file a JIRA issue online in the Subversion JIRA plugin project.
News
0.10.3 Released
Fixed a bug where ssh+svn would not work due to an incompatible SSH library being shipped with the plugin (SVN-199).
0.10.2 released
Several improvements and a bug fix.
- The plugin now process issue keys in commit messages in case-insensitive manner. (SVN-93)
- The plugin now officially supports the file protocol. (SVN-38)
- Fixed a bug where the web link format could not be changed. (SVN-190)
0.10.1 released
Fixed a bug where the plugin would never automatically reactivate after it had deactivated due to a SVN connection failure (SVN-181), and improved error logging (SVN-174).
0.9.12 released
Changes for upgrading Lucene in JIRA v3.11. Incompatible with previous versions.
0.9.11 released
No changes, upped source dependencies for JIRA v3.10.
0.9.10 released
Contains a fix for SVN-133(commit data does not follow Project Permission Scheme - honoring current assignee and reporter) and upped source dependencies for JIRA v3.9.
0.9.9 released
No changes, upped source dependencies for JIRA v3.8.
0.9.8 released
No changes, except that the sample properties file now works out the box against svn.atlassian.com.
0.9.7 released
Contains a fix for SVN-123, a problem affecting people importing data with a new index path.
0.9.6 released
Latest version tested for compatibility with JIRA 3.7.
Subversion location moved
Please note the slightly different Subversion location of this plugin:
- If you have the plugin checked out at its old location, run svn switch http://svn.atlassian.com/svn/public/contrib/jira/subversion-jira-plugin/trunk
- To check the latest version of the plugin out from Subversion, run svn checkout http://svn.atlassian.com/svn/public/contrib/jira/subversion-jira-plugin/trunk/ subversion-jira-plugin.
0.9.5 released
The Plugin now features a new project tab, which shows all commits made against a particular project or a project version, giving you a summary of recent developer activity on the project. (Screenshot below)
0.9.4 released
Fixed SVN-102, allowing multiple SVN directories from a single repository.
 |
Note: From version 0.9.4+ you will have to delete your already indexed subversion logs and let the plugin re-index since we have changed the stored repository id in the index document. (Fixes SVN-102. If you do not use multiple directories from one repository, you do not need to make this update). Please ensure that you delete the subversion plugin index directory and its contents - e.g. <JIRA-INDEX-DIR>/plugins/atlassian-subversion-revisions. |
0.9.3 released
Updated to version 1.0.5 of the javasvn library to fix issues JRA-10148 and SVN-13 which caused problems including a repository via http with a url with no
context path.
0.9.2 released
Minor updates for compatibility (services) with JIRA 3.6.
0.9.1 released - Now includes the javasvn and ganymed libraries
We have licensed the javasvn library and can now redistribute it, so this release includes all the libraries you will need to get this plugin up and running.
0.9 released - Updated to use latest version of javasvn, works against subversion 1.3
In the 0.9 release we have updated our dependency on the javasvn jar to version 1.0.3. This allows us to work with subversion 1.3 without any issues. The license of the javasvn library has changed from 0.8.8 and 1.0.3. We can now no longer distribute the library with our plugin since it would be "for commercial use". Our install instructions have therefore changed and you must now download the javasvn.jar on your own. This change is still backward compatable with all previous subversion versions.
0.8.1 released - Bug fix to address JRA-8336
In the 0.8.1 release we fix some issues that were affecting the links into viewcvs that were generated. The subversion-jira-plugin.properties contains some updated sample property url's for viewcvs that you should apply to your properties file.
0.8 released - ViewCVS URL now fully configurable
In the 0.8 release the URL format is now fully configurable in the subversion-jira-plugin.propertiesfile, so we can support both old and new-style ViewCVS URLs, as well as Fisheye and other systems in future. Thanks to Lu Chenggong for the initial patch (SVN-46). The subversion-jira-plugin.properties format is not backwards-compatible - please reapply your customizations to the sample properties file.
0.6 released - Multiple repository support
Note: You will have to delete your already indexed subversion logs and let the plugin re-index since we now include the repository id in the index document. Thanks to ngrabova for some code contributions towards multiple repository support.
Comments (244)
Nov 18, 2004
Brendan Doherty says:
Here is my apache log for the requests from JIRA, could anyone tell me if it is ...Here is my apache log for the requests from JIRA, could anyone tell me if it is working correctly? it doesnt seem to be picking up the commit messages, but it doesnt throw any errors either?
"note: the first time the service runs it will take a while to index all of your existing issues - be patient" - How long is a while 2/3 hours more?
IP - username [18/Nov/2004:17:19:37 +0000] "PROPFIND /repos HTTP/1.1" 207 641
IP - username [18/Nov/2004:17:19:37 +0000] "PROPFIND /repos/!svn/vcc/default HTTP/1.1" 207 392
IP - username [18/Nov/2004:17:19:38 +0000] "PROPFIND /repos/!svn/bln/6 HTTP/1.1" 207 443
Nov 18, 2004
Mike Cannon-Brookes says:
Brendan, If you turn up the logging level in JIRA you should see more informati...Brendan,
If you turn up the logging level in JIRA you should see more information from the plugin.
The easiest way to do this is to edit WEB-INF/classes/log4j.properties within the web application and add something like:
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console log4j.category.com.atlassian.jira.plugin.ext.subversion.additivity = falseThat should enable all debug logging from the Subversion plugin, which will tell you what it is trying to retrieve from your Subversion server, which changes it matched to issues etc.
Let us know how you go.
Cheers,
Mike
Oct 28, 2007
AJ says:
<b> Hi , Is there a way to hide the 'Subversion Commit' tab from Users. We would...<b> Hi , Is there a way to hide the 'Subversion Commit' tab from Users. We would want only our developers and QA to view this tab.</b>
Oct 29, 2007
Ian Daniel [Atlassian] says:
Hi AJ, There is a View Version Control permission in the permission scheme. Mak...Hi AJ,
There is a View Version Control permission in the permission scheme. Make sure that normal users don't have it. That should do the trick.
Kind regards,
Ian
Nov 19, 2004
Brendan Doherty says:
cheers mike will try it outcheers mike will try it out
Nov 19, 2004
Brendan Doherty says:
Hi Mike, I added those 2 lines to log4j.properties and it didnt make any differ...Hi Mike,
I added those 2 lines to log4j.properties and it didnt make any difference to the output in stdout.log. With the other class-specific logging levels I can switch them off and on and it is reflected in stdout.log. Any idea what I am doing wrong.
thanks
Bren
Nov 27, 2004
Anonymous says:
When working with Subversion without user names, meaning, that the commits are A...When working with Subversion without user names, meaning, that the commits are Anonymous, the [ext.subversion.revisions.RevisionIndexService] throws a NullPointerException.
Only when the subversion revision has a username associated to it, the plugin works.
Nov 29, 2004
Mike Cannon-Brookes says:
I have a feeling this is related to SVN9@JIRA which is fixed in 0.5. Thanks for ...I have a feeling this is related to SVN-9 which is fixed in 0.5. Thanks for the report - let us know if 0.5 doesn't fix it.
Dec 01, 2004
Anonymous says:
each of our projects uses a separate svn repository (located on the same server,...each of our projects uses a separate svn repository (located on the same server, but at a different path) - how do I set up the plugin to work with multiple repositories ?
josh
Dec 08, 2004
Anonymous says:
We're also structuring our repositories this way is multiple repository handling...We're also structuring our repositories this way - is multiple repository handling a planned feature in the JIRA SVN plugin?
Steph
Mar 24, 2005
Anonymous says:
I see nobody has answered this yet, so let me state my desire for an answer to t...I see nobody has answered this yet, so let me state my desire for an answer to this. We've got several projects, each with their own Subversion repository (all on a single server) and a single JIRA. How can we configure multiple repositories for the plugin?
Dec 07, 2004
Gene Sohn says:
This is great to see!! I'm trying to get this to workjust downloaded 0.5. Not su...This is great to see!! I'm trying to get this to work--just downloaded 0.5. Not sure how the "subversion commits" tab gets its info. Can you clarify what the "workflow" is that ultimately gets something in there?
Dec 21, 2004
Mark Stanton says:
Hey Guys I might be smoking crack but at 9.30pm here is what I have noticed. I...Hey Guys
I might be smoking crack but at 9.30pm here is what I have noticed.
In here our SVN root is http://svn.blah.int. This works fine in my other SVN tools.
0.5 does not work when the repo is actually a root domain - everything is sweet if is your svn.root is a subdirectory (http://svn.blah.int/projectname), but when its pointing to the domain itself (http://svn.blah.int or http://svn.blah.int/) I'm getting the plugin trying to parse the string "HTML" as an HTTP status code (integer). Here is the output in stdout.log:
21/12/2004 21:39:35 com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl setupEnvironment
SEVERE: Could not load properties from subversion-jira-plugin.properties
java.lang.NumberFormatException: For input string: "HTML"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at org.tmatesoft.svn.core.internal.io.dav.DAVStatus.parse(DAVStatus.java:37)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.readHeader(HttpConnection.java:360)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.sendRequest(HttpConnection.java:147)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.sendRequest(HttpConnection.java:125)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.request(HttpConnection.java:119)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doPropfind(DAVConnection.java:71)
at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:30)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:50)
I've tried setting up an alias in apache (Alias /repo etc...) so that I can refer to the root as a subdirectory. So http://svn.blah.int/repo now points back at the SVN root. This works in my other SVN tools. svn.root now points to http://svn.blah.int/repo/ or http://svn.blah.int/repo (tried both).
When I start up tomcat, I get an HTTP 301 in the stdout.log:
21/12/2004 21:37:20 com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl setupEnvironment
SEVERE: Connection to Subversion repository failed: org.tmatesoft.svn.core.io.SVNException: server reports an error: 301:Moved Permanently
etc…
I'd expect http://svn.blah.int/repo to result in a 301, but I'd expect http://svn.blah.int/repo/ to be 200. However it looks like the trailing slash is getting dropped before the request (according to the apache logs).
Wasn't really sure whether to post this as an issue, to the list or here - so let me know.
Mark
Dec 30, 2004
Anton Mazkovoi says:
Mark, Thank you for reporting the problem. I have replicated it locally and log...Mark,
Thank you for reporting the problem. I have replicated it locally and logged it here for tracking: SVN-13
Unfortunately we are short on staff at the moment due to holidays, however we should be able to get to early in the new year.
Thanks,
Anton
Jan 19, 2005
Mark Stanton says:
Just following up on this Colin Bendell kindly posted a patch which works for me...Just following up on this - Colin Bendell kindly posted a patch which works for me. The patch is downloadable from http://jira.atlassian.com/browse/SVN-13.
On another note - I've had my developers religiously putting JIRA issue id's in all their commit comments for the past few weeks. Now that we have the SVN plugin working I was expecting JIRA to parse through all this historical data, but it only seems to be looking at the past 6 hours or so.
Anyway ideas?
Jan 03, 2005
Anonymous says:
I've downloaded the subversion module, and configured to use a local repository ...I've downloaded the subversion module, and configured to use a local repository (svn://localhost/), but when I click the tab for SubversionCommits, it is blank. Log only ever says: [atlassian.jira.vcs.DefaultRepositoryManager] No repository defined for project
Have I misconfigured something?
Jan 24, 2005
David Peterka says:
LDAP? We're running Subversion through Apache2 and using ldap. The Jira plugin ...LDAP?
We're running Subversion through Apache2 and using ldap. The Jira plugin returns an error and watching the apache logs I see A) no authentication error in error_log B) 401 error returns from the JIRA server. Is it possible Jira is unable to authenticate via this method?
____________________________
Jira error >
SEVERE: Connection to Subversion repository failed: org.tmatesoft.svn.core.io.SVNException: can't connect
org.tmatesoft.svn.core.io.SVNException: can't connect
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.sendRequest(HttpConnection.java:186)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.sendRequest(HttpConnection.java:125)
at org.tmatesoft.svn.core.internal.io.dav.HttpConnection.request(HttpConnection.java:119)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doPropfind(DAVConnection.java:71)
at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:30)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:50)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:260)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:56)
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.setupEnvironment(SubversionManagerImpl.java:106)
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.<init>(SubversionManagerImpl.java:42)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:100)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:200)
at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:27)
at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)
at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstances(DefaultPicoContainer.java:266)
at com.atlassian.jira.ComponentManager.eagerlyInstantiate(ComponentManager.java:271)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:197)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3271)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3613)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:754)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:363)
at org.apache.catalina.core.StandardService.start(StandardService.java:497)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190)
at org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245)
at org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307)
Jan 25, 2005
Adam Turk says:
Well, it's using svnserve, so just internal subversion authentication. I was thi...Well, it's using svnserve, so just internal subversion authentication. I was thinking that it seemed similar to CVS repositories in Jira, but there is not a place in "project edit" to attach an SVN repository. I am stumped by this.
Jan 25, 2005
David Peterka says:
Maybe of note: If I add a trailing slash in .properties I get the above results,...Maybe of note: If I add a trailing slash in .properties I get the above results, if I remove the slash I get two errors from Apache, an authentication failure and a 'collection does not accept requests without trailing slashes' (this is not exact haven't set up the scenario again), the Jira error remains the same.
Feb 11, 2005
Anonymous says:
Last update in November, 2004. Is it stuck at 0.5? K>Last update in November, 2004. Is it stuck at 0.5?
K>
Feb 22, 2005
Anonymous says:
I'm using the subversion jira plugin with Subversion 1.1.3 and Jira 3.1. I down...I'm using the subversion jira plugin with Subversion 1.1.3 and Jira 3.1.
I downloaded the latest version .5 and followed the directions. When I started up the jira application again I kept getting the Exception:
"SEVERE: Connection to Subversion repository failed: org.tmatesoft.svn.core.io.SVNException: network data doesn't match template, expected (, read ? (65535)"
So I upgraded the JavaSVN jar from the one in the .5 distribution to the newest 0.8.3 release and it seems to be working.
But now when I look at revisions in the Subversion Commit Panel in Jira the link url to the revision number (e.g. #23) ends in /viewsvn/svn?&view=rev&rev=24 rather than viewsvn?view=rev&rev=24 where viewsvn is my scriptalias to viewcvs.cgi. Have any idea why this is happening?
Feb 22, 2005