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 | 3.13 | 4.0 | Tested |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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) | |||||||||||
| 0.10.4 | |
|
|
|
Brad Baker (Sep/02/2008) | ||||||||||
| 0.10.4.1 | |
|
|
|
David Chui (Jan/21/2009) | ||||||||||
| 0.10.4.2 | |
|
|
|
Paul Mansfield | ||||||||||
| 0.10.5 | |
David Chui (Oct/06/2009) | |||||||||||||
| 0.10.5.1 | |
David Chui (Oct/09/2009) | |||||||||||||
| 0.10.5.2 | |
David Chui (Oct/09/2009) |
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 file, 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
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)

If you're using 0.10.3 of this plugin, make sure your remove the javasvn and ganymed jars from JIRA's WEB-INF/lib directory.
- Copy subversion-jira-plugin.properties into JIRA's WEB-INF/classes.
- In the same location where subversion-jira-plugin.properties would be, open jira-application.properties (for WAR distribution, copy it to edit-webapp) and set jira.option.ignore.url.with.key=false.
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.
Uninstall Instructions
- Go to JIRA's administration console, then to Services. Remove the Subversion service from there.
- Shutdown JIRA.
- Remove the files that were copied to JIRA's WEB-INF/lib directory when you installed the plugin. They are:
- atlassian-subversion-plugin-*.jar
- javasvn-*.jar (if any)
- svnkit-*.jar (if any)
- ganymed-*.jar (if any)
- trilead-*.jar (if any)
- Remove the the subversion-jira-plugin.properties file from WEB-INF/classes.
- Remove the plugin's index files by going to the plugins directory in JIRA's index directory. Then remove the atlassian-subversion-revisions directory.
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.
- E.g. If you need to configure Tomcat to pass your firewall, add the following parameters to the SET JAVA_OPTS= command in startup.bat:
-Dhttp.proxyHost=your-proxy-address -Dhttp.proxyPort=80
- E.g. If you need to configure Tomcat to pass your firewall, add the following parameters to the SET JAVA_OPTS= command in startup.bat:
- 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 the plugin is having problems authenticating towards your subversion repository, and the repository is using the credentials in an LDAP server, please try the workaround specified in SVN-240.
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.
Version History
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 (320)
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:
That 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...<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 SVN-9 which is fixed in 0.5. Thanks for the ...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 handli...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 work--just downloaded 0.5. No...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 ...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
Anonymous says:
The above post is mine. I'm using the latest 1.0-dev CVS build from Sunday Feb 2...The above post is mine.
I'm using the latest 1.0-dev CVS build from Sunday Feb 20th 2005. The problem seems to be in the class com.atlassian.jira.plugin.ext.subversion.linkrenderer.ViewCVSLinkRenderer
in the linkRevision(long revisionNumber) method.
Has ViewCVS possibly changed the way they link to revision in Subversion?
Adam Kramer
Feb 22, 2005
Daniel Leuck says:
The plugin is great, but we really need it to work with multiple repositories.The plugin is great, but we really need it to work with multiple repositories.
Mar 18, 2005
Mariano Peterson says:
Help!? I can't get this plugin working on my copy of JIRA. I don't see any err...Help!? I can't get this plugin working on my copy of JIRA. I don't see any error messages in catalina.out, but when I go to the Subversion tab it doesn't report the svn commits related to the JIRA incident.
My environment:
OSX Server 10.3
Java 1.4.2_05
JIRA Professional Edition v3.1.1
Subversion 1.1.1 (svnserve and the svn repository are on the same server as JIRA)
JIRA Subversion Plugin 0.5
I've configured subversion-jira-plugin.properties so that the plugin connects to subversion via svn+ssh://localhost/<path to repos>. I've also set the svn.username and svn.password properties to a valid user/password who can connect to subversion from the command line on the JIRA server. I've also stopped JIRA, deleted ...Index/plugins/atlassian-subversion-revisions/, and then started JIRA back up.
I've updated log4j.properties so that log4j.rootLogger and log4j.category.com.atlassian.jira.plugin.ext.subversion are at DEBUG. I've also set log4j.category.com.atlassian.jira.plugin.ext.subversion.additivity = false.
Searching within JIRA/logs/, the only places where subversion is mentioned are in atlassian-jira.2005-03-18.log
(2005-03-18 20:53:30 WebappLoader[]: Deploy JAR /WEB-INF/lib/atlassian-jira-subversion-plugin-0.5.jar to /Applications/JIRA/webapps/../atlassian-jira/WEB-INF/lib/atlassian-jira-subversion-plugin-0.5.jar)
and catalina.out:
([WARN] LuceneUtils - -Directory /Library/Application Support/JIRA/Index/plugins/atlassian-subversion-revisions does not exist - perhaps it was deleted? Creating..)
2005-03-18 21:32:51,903 DEBUG [atlassian.jira.service.ServiceRunner] Running Service [Container: com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService This service indexes Subversion revisions. delay [120000ms]]
2005-03-18 21:33:00,200 DEBUG [atlassian.jira.service.ServiceRunner] Finished Running Service [Container: com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService This service indexes Subversion revisions. delay [120000ms]]
I'm not getting much from the logs. Any ideas?
Mar 18, 2005
Mariano Peterson says:
I've also noticed the following in /var/log/system.log: Mar 18 21:51:36 <HOS...I've also noticed the following in /var/log/system.log:
Mar 18 21:51:36 <HOST> SystemStarter: Restarting JIRA
Mar 18 21:51:38 <HOST> SystemStarter: Startup complete.
Mar 18 21:52:23 <HOST> xinetd[429]: service ssh, IPV6_ADDRFORM setsockopt() failed: Protocol not available (errno = 42)
Mar 18 21:52:23 <HOST> xinetd[429]: START: ssh pid=11104 from=192.168.6.26
Mar 18 21:52:25 <HOST> sshd[11104]: Accepted password for <SVN_USER> from 192.168.6.26 port 52959 ssh2
Mar 21, 2005
Brian Lalor says:
What changed from 0.5 -> 0.5.1?What changed from 0.5 -> 0.5.1?
Mar 28, 2005
Keith says:
Hi Brian, The only update was to incorporate the latest JavaSVN libraries (0.8....Hi Brian,
The only update was to incorporate the latest JavaSVN libraries (0.8.6).
Regards,
Keith
Mar 25, 2005
Yoshia Makino says:
I have a fairly large repository that I need to index and it seems that each ite...I have a fairly large repository that I need to index and it seems that each iteration of the service only runs for around 1200 revisions. Unfortunately, the earlier stuff has nothing that can be indexed and so, the RevisionIndexer runs over the same 1200 revisions or so everytime since the last revision is stuck to the last indexed revision.
ie. revision 1000 was last indexed. The next service interation runs to 2200 but nothing is found so last indexed revision is stuck at revision 1000 and all subsequent service runs starts from 1000 again. I haven't spent a whole time on this so any help you can give me before I start hacking away at the code would be appreciated. Thanks
Mar 25, 2005
Yoshia Makino says:
I dug into the code and found out that it was a problem with the javasvn library...I dug into the code and found out that it was a problem with the javasvn library. HttpConnection.readResponse eats a SAXException and goes on its merry way without giving us a peep. Oh well.
Apr 06, 2005
Ahmad Masrieh says:
Community, what about linking the planned JIRA support for build numbers http:/...Community,
what about linking the planned JIRA support for build numbers http://jira.atlassian.com/browse/JRA-568
to the revision feature of subversion and e.g. auto-creation of versions within JIRA projects ...?
Ahmad
Apr 14, 2005
Anonymous says:
Will the plugin support the upcomming Subversion 1.2 release?Will the plugin support the upcomming Subversion 1.2 release?
May 22, 2005
ace says:
is it possible to use this plug-in with jira and subversion at two different ser...is it possible to use this plug-in with jira and subversion at two different servers?
Jun 01, 2005
Anonymous says:
Does this plugin work on 3.2? And I'll second the question about subversion 1.2....Does this plugin work on 3.2? And I'll second the question about subversion 1.2.
It looks like ti will do what we need if so.
Jun 02, 2005
Anonymous says:
Hi, I have a logfile entry in svn which is clearly not being picked up by the p...Hi,
I have a logfile entry in svn which is clearly not being picked up by the plugin:
e.g.
---------- cut here -------------
Activate Scheduer list.
added:
activate scheduer script.
For script descriptions look in https://localhost/doc/scripts%20description.doc
TEST-101, TEST-102
---------- cut here -------------
What's interesting is that TEST-102 does pick up the log file, but TEST-101 does not. Without looking in the code it appears that there's some kind of parsing irregularity in this case. Can someone look into this, please?
Thanks!!
Gene
Jun 03, 2005
Anonymous says:
The revision URL for viewcvs is wrong, it makes the url: The url is configured ...The revision URL for viewcvs is wrong, it makes the url:
The url is configured int he properties file as: http://host/viewcvs/
The files themselves are linked properly in jira as: http://host/viewcvs/trunk/rest/of/the/path/to/file
But the revision link is being linked as: http://host/viewcvs/svn?view=rev&rev=num
which is incorrect, should be: http://host/viewcvs/?view=rev&rev=num
This is in verion 0.6
Jun 09, 2005
Anonymous says:
Yes, I can confirm this, the revision links are not working. There is an issue a...Yes, I can confirm this, the revision links are not working. There is an issue about it here: http://jira.atlassian.com/browse/SVN-18
Another issue with the ViewCVS links is that if the file has been removed in a later revision the link does not work. The link should contain a reference to the revision, like this: http://host/viewcvs/trunk/rest/of/the/path/to/file?rev=794&view=markup
/Anders
Jun 09, 2005
Matt Barrett says:
Hi I just had a look at http://jira.atlassian.com/browse/SVN-18 which pointed m...Hi
I just had a look at http://jira.atlassian.com/browse/SVN-18 which pointed me in the right direction to fix my own problem: getting the Subversion plugin to render links correctly to WebSVN revisions.
The code change is trivial - but how do I go about recompiling the Subversion extension? Do I need the rest of the Jira source code to do that?
Jun 13, 2005
Burt Smith says:
And to help those who are using 0.6 and want their cross-reference links not to ...And to help those who are using 0.6 and want their cross-reference links not to be broken, I've added some info about a temporary workaround that will allow them to work somewhat. That also is at the JIRA entry for SVN-18: http://jira.atlassian.com/browse/SVN-18.
Jun 21, 2005
Anonymous says:
How to integrate Subversion repository and JIRA? Where i want to configure. I ha...How to integrate Subversion repository and JIRA?
Where i want to configure. I had aready installed all the required plugin in the lib folder.
Help me ?
Anand
Jun 24, 2005
Anonymous says:
I have a Jira 3.0.3 install with 10 projects. I installed the subversion plugi...I have a Jira 3.0.3 install with 10 projects.
I installed the subversion plugin and it works for 9 of the 10 projects.
For the 10th, whenever an issue is viewed the following is logged:
[web.action.issue.ViewIssue] Unknown tab panel 'com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel' has been specified.
Any idea why the plugin wouldn't be working for this project but working for all the others?
thanks for jira,
-m
Jun 28, 2005
Dylan Etkin says:
Hi, Could open an issue on support.atlassian.com for this and attatch your serve...Hi, Could open an issue on support.atlassian.com for this and attatch your server log and your subversion-jira-plugin.properties file? How many svn repositories do you have configured? Do you have any special schemes associated with the offending project?
Thanks,
Dylan
Jun 28, 2005
Anonymous says:
No issue to be reported. The 'view version control' permission was empty... ...No issue to be reported.
The 'view version control' permission was empty...
typical,
-m
Jun 30, 2005
Anonymous says:
Hi I got the plugin to work and it indexed my repository when I re-deployed JIR...Hi
I got the plugin to work and it indexed my repository when I re-deployed JIRA...But any commits after that did not show...I tried flushing the chache and re-indexing in JIRA but that didn't help....
How ofter is Lucene index created for Subversion plugin?
Is there a way I can force re-index of atlassian-subversion-revisions/ ?
Thanks
Jul 01, 2005
Anonymous says:
Came in this morning to work and revision index was updated, so I was able to se...Came in this morning to work and revision index was updated, so I was able to see my Subversion commits/changes....
Still, is there a way to controll how often revision index is updated?
Thanks
Jul 02, 2005
Mike Cannon-Brookes says:
You can control how often the revision index is updated by editing the service p...You can control how often the revision index is updated by editing the service period (Administration > System > Services I believe). The default is 1 hour.
Jul 07, 2005
Anonymous says:
Ahhh Very Nice...I totally missed this. Maybe it should be mentioned in one fo ...Ahhh
Very Nice...I totally missed this. Maybe it should be mentioned in one fo the paragraphs after Install section of the docs?
Anyway, thanks a lot
Apr 14, 2006
Marilyn Daum says:
Yes, please mention the Subversion Revision Indexing Service setting with the in...Yes, please mention the Subversion Revision Indexing Service setting with the installation instructions. I spent quite awhile trying to figure out why my test commits weren't showing up before I finally found this set of comments.
Jun 30, 2005
Indiver Nagpal says:
I think I am missing something very simple! I can't figure out the syntax of th...I think I am missing something very simple!
I can't figure out the syntax of the properties file.
I have multiple SVN repositories, which require user authentication.
For example, how would I modify the properties file I was to add following two SVN repositories?
Both have a user called "abc", with password "123"
Thanks
Jun 30, 2005
Indiver Nagpal says:
Doh! I was looking at the project.properties files... Please excuse my trying...Doh!
I was looking at the project.properties files...
Please excuse my trying to setup the plugin late in the evening after a couple of drinks
Will try changing the subversion-jira-plugin.properties files now.
Jun 30, 2005
Indiver Nagpal says:
Got it going! Very cool! Thanks guys.Got it going!
Very cool! Thanks guys.
Jul 15, 2005
Lance Speelmon says:
We have the 0.6.1 plugin installed on JIRA Enterprise Edition, Version: 3.1-#80....We have the 0.6.1 plugin installed on JIRA Enterprise Edition, Version: 3.1-#80. Getting ViewCVS to support subversion was the hardest part...
Take a look:
http://bugs.sakaiproject.org/jira/browse/SAK-1429
Nice job Atlassian!
Jul 15, 2005
Mike Cannon-Brookes says:
Good job! But it looks like the View Version Control permission is not set to An...Good job! But it looks like the View Version Control permission is not set to Anyone - hence it's only visible to logged in users!
Jul 15, 2005
Lance Speelmon says:
That does seem to be true. We would like to expose the Subversion Commits to an...That does seem to be true. We would like to expose the Subversion Commits to anonymous or authenticated users. Does anyone know if this is a setting that can be changed or is it a limitation of the plug-in? Thanks, L
Jul 18, 2005
Lance Speelmon says:
Never mind... Our JIRA admin found the setting. Thanks! LNever mind... Our JIRA admin found the setting. Thanks! L
Jul 15, 2005
Lance Speelmon says:
We seem to be having a problem with the plug-in detecting commits when the commi...We seem to be having a problem with the plug-in detecting commits when the commit log messages contain the issue key in the following format: http://bugs.sakaiproject.org/jira/browse/SAK-1401
Any thoughts on how this can be resolved? Thanks, L
Jul 19, 2005
Lance Speelmon says:
FYI, I filed a bug report on this issue: http://jira.atlassian.com/browse/SVN-37FYI, I filed a bug report on this issue: http://jira.atlassian.com/browse/SVN-37
Aug 15, 2005
Keith says:
NOTE: The 0.7.1 release merely ensures that all version numbers are correct - i....NOTE: The 0.7.1 release merely ensures that all version numbers are correct - i.e. the version and JIRA dependency info within atlassian-plugin.xml are correct.
Aug 23, 2005
Lance Speelmon says:
Could you please tell us what changed between 0.6.1 and 0.7.0? Thanks, LCould you please tell us what changed between 0.6.1 and 0.7.0? Thanks, L
Aug 25, 2005
Keith says:
Hi Lance, The subversion plugin underwent minor changes between these versions ...Hi Lance,
The subversion plugin underwent minor changes between these versions - in the area of error handling:
*Improved error handling if repositories are unreachable
Let us know if you require any further information.
Regards,
Keith
Aug 31, 2005
Craig McElroy says:
Found the following documentation page regarding using JavaSVN (the backend libr...Found the following documentation page regarding using JavaSVN (the backend library of the Subversion JIRA plugin) with svn+ssh with private key instead of a password.
http://tmate.org/svn/kb/config-settings.html
Adding -Djavasvn.ssh2.key=/path/to/private/key/file to the JIRA startup command worked like a champ.
Sep 01, 2005
Bill de hOra says:
The plugin isn't working for me with a https + basic-auth combination. Is that c...The plugin isn't working for me with a https + basic-auth combination. Is that combination known to work as of v0.7.1?
From the (modded) properties file:
svn.root=https://$domain/svn/reposname/
svn.display.name=reposname
svn.username=$username
svn.password=$password
revision.indexing=true
revision.cache.size=1000
On startup I get a stacktrace telling me the connection was refused (modded):
2005-09-02 00:32:39,318 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://$domain/svn/reposname/ failed: org.tmatesoft.svn.core.io.SVNException: java.net.ConnectException: Connection refused
org.tmatesoft.svn.core.io.SVNException: java.net.ConnectException: Connection refused
I can verify the properties details are correct. I've also tried the plugin with the latest javasvn release, which made no difference.
Sep 06, 2005
Keith says:
Hi Bill, I have verified that v0.7.1 works correctly with https + Basic Authent...Hi Bill,
I have verified that v0.7.1 works correctly with https + Basic Authentication. Can you check the svn.root property - I think this may work if you edit it to be:
svn.root=https://$domain/reposname
Sep 16, 2005
BJ Blackburn says:
I am evaluating JIRA Enterprise. So far it looks very good, but I can’t get the ...I am evaluating JIRA Enterprise. So far it looks very good, but I can’t get the subversion plugin working.
I have searched the mailing lists and the plugin page for help, with no luck. I am using JIRA 3.3.1 and 0.7.1 of the subversion plugin. When the plugin is installed the indexer runs once successfully – I have confirmed this both by viewing a test issue and actually seeing commit info on the proper tab, as well as by placing the plugin into debug and viewing the log.
The next time the service delay period comes around, it appears as if an attempt is made to retrieve information, but nothing happens, from that point, no further activity occurs and no errors are ever thrown. Restarting the web app causes this cycle to repeat (and any recent commits to be indexed), but of course restarting the app is not a viable workaround. Please help me if you can.
I am using svn+ssh://username@hostname/reposname plus a user id and password to access the repository. The evaluation env is windows XP, java 1.5, tomcat 5.5, and mysql 4.1
Below is the tail end of the log, after the last entry, nothing will happen again until a restart:
2005-09-16 12:08:22,803 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieved 3 relevant revisions to index (between 0 and 1377) from repository=2db7d1f7-5cf5-0310-8ef0-800000000000
2005-09-16 12:08:22,803 DEBUG [ext.subversion.revisions.RevisionIndexer] log entries size = 3 for 2db7d1f7-5cf5-0310-8ef0-800000000000
2005-09-16 12:08:22,819 DEBUG [ext.subversion.revisions.RevisionIndexer] Indexing repository=2db7d1f7-5cf5-0310-8ef0-800000000000, revision: 380
2005-09-16 12:08:22,834 DEBUG [ext.subversion.revisions.RevisionIndexer] Indexing repository=2db7d1f7-5cf5-0310-8ef0-800000000000, revision: 381
2005-09-16 12:08:22,834 DEBUG [ext.subversion.revisions.RevisionIndexer] Indexing repository=2db7d1f7-5cf5-0310-8ef0-800000000000, revision: 1377
2005-09-16 12:16:03,444 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieving revisions for : JIR-3
2005-09-16 12:16:03,444 DEBUG [plugin.ext.subversion.SubversionManagerImpl] No cache - retrieving log message for revision: 1377
2005-09-16 12:20:29,803 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieving revisions for : JIR-4
2005-09-16 12:20:33,147 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieving revisions for : JIR-4
2005-09-16 12:21:06,787 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieving revisions for : BIGKEY-1
2005-09-16 13:09:17,147 DEBUG [ext.subversion.revisions.RevisionIndexer] RevisionIndexer.createIndexIfNeeded()
2005-09-16 13:09:17,147 DEBUG [ext.subversion.revisions.RevisionIndexer] repos size = 1
2005-09-16 13:09:17,147 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating revision index for repository=2db7d1f7-5cf5-0310-8ef0-800000000000
2005-09-16 13:09:17,147 DEBUG [ext.subversion.revisions.RevisionIndexer] 16 Sep 2005 20:09:17 GMT Updating revision index for repository=2db7d1f7-5cf5-0310-8ef0-800000000000
2005-09-16 13:09:17,147 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating last revision indexed.
2005-09-16 13:09:17,178 DEBUG [ext.subversion.revisions.RevisionIndexer] latestIndRev for 2db7d1f7-5cf5-0310-8ef0-800000000000 = 1377
2005-09-16 13:09:17,178 DEBUG [ext.subversion.revisions.RevisionIndexer] Latest indexed revision for repository=2db7d1f7-5cf5-0310-8ef0-800000000000 is : 1377
2005-09-16 13:09:17,866 DEBUG [ext.subversion.revisions.RevisionIndexer] Latest revision in repository=2db7d1f7-5cf5-0310-8ef0-800000000000 is : 1378
2005-09-16 13:09:17,866 DEBUG [ext.subversion.revisions.RevisionIndexer] Retrieving revisions to index (between 1378 and 1378) for repository=2db7d1f7-5cf5-0310-8ef0-800000000000
Sep 18, 2005
BJ Blackburn says:
Follow up: After leaving this alone for a while, the indexer suddenly starte wo...Follow up:
After leaving this alone for a while, the indexer suddenly starte working again, running every hour and leaving behind log messages that seemed to indicate success. I then used JIRA to slect and display an issue for which I knew there was a list of commits – at that point, I was also watching the log and saw a message indicating that the selected issue was not in the cache and that it would be retrieved, but it never was, and in fact the issue was never displyed in the browser at all, it just stopped while 'waiting for [servername]...' Thi was especially confounding as the wating never timed out and no messages were ever entered in the log.
I then stopped tomcat, and deleted the index. After starting it up again, and waiting for the indexer to go through its initial run again, I again tried to access an issue, first choosing one I knew had no svn hostory at all – it displayed fine. I then selected one that did have history and it never displayed, same behavior as described above with the browser shoing 'waiting for [servername]...' forever and the log indicating that the commit was being retreived.
It appears to me that the code that is handling the connection to svn is failing, but failing completelt silently.
Sep 19, 2005
Jeff Turner says:
If you run the SVN checkout command over SSH from the command-line, does it work...If you run the SVN checkout command over SSH from the command-line, does it work?
These comments aren't really meant for usage problems. Please could you raise a support request on http://support.atlassian.com, and attach anything relevant.
In particular, please run 'kill -3 <pid>' (Unix) or ctrl-break (Windows) to generate a thread dump when JIRA is hanging trying to retrieve a SVN log, and that will show what it is doing. Also, if you can use a packet sniffing tool like ethereal, that would be helpful in working out what is happening.
Cheers,
Jeff
Sep 22, 2005
Jerome Lacoste says:
Some notes: we use svn+ssh and it works , contrary to what the README says. ...Some notes:
Feel free to post an answer to http://www.coffeebreaks.org/blogs/?p=16
Sep 22, 2005
Anton Mazkovoi says:
Hi Jerome, Thanks for the good pointers. svn+ssh is supported and we have upda...Hi Jerome,
Thanks for the good pointers.
svn+ssh is supported and we have updated our README.txt file. Thanks again for the tip.
For information on how to restrict access of the ssh user used for svn access see this page. It talks about CVS, but I am sure that it can be adapted for subversion.
Thanks,
Anton
Sep 22, 2005
Anton Mazkovoi says:
I believe the command that gets run over ssh is: svnserve --tunnel I have n...I believe the command that gets run over ssh is:
svnserve --tunnel
I have not tried it. Please let us know if it works for you.
Thanks,
Anton
Sep 29, 2005
Anonymous says:
Hi I want to create a report, relying on the subversion revision number. I can ...Hi
I want to create a report, relying on the subversion revision number. I can see the number inside Jira on the plugin page, but I can not integrate it into my view definition.
Is it possible to use the plugin data in Jira queries?
Thanks
Jan
Sep 29, 2005
Jeff Turner says:
The Subversion plugin does 'export' its Manager object via Picocontainer, as you...The Subversion plugin does 'export' its Manager object via Picocontainer, as you can see in its atlassian-plugin.xml:
<component key="subversionManager" name="subversion Manager" class="com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl">
<interface>com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManager</interface>
</component>
So if you request a MultipleSubversionRepositoryManagerImpl in your Pico-instantiated class (Webwork action) or request it as is done in ComponentManager.java, you should be able to get SVN revision numbers for issues.
Cheers,
Jeff
PS: In future, please ask general questions on jira-support@atlassian.com instead of these comments.
Oct 28, 2005
Anonymous says:
Hi, just wondering why I can't make the project repository settings inside jira...Hi,
just wondering why I can't make the project repository settings inside jira. Redeploying/ restarting the app is not very nice...
And, keeping information twice is not fun as well.
brgds,
P.G.Taboada
Oct 30, 2005
Anton Mazkovoi says:
Unfortunately we have not had the chance to do this yet. Please vote for: http:/...Unfortunately we have not had the chance to do this yet. Please vote for: http://jira.atlassian.com/browse/SVN-51
to increase its popularity.
Please refer to this document which explains the way we schedule new features: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements
Nov 04, 2005
Anonymous says:
Hi, first I would like to thank you for this wonderful plugin. Here is my ques...Hi,
first I would like to thank you for this wonderful plugin.
Here is my question:
We use a customized Jira Excel export template to generate our release notes. The missing piece of the puzzle is to include the Subversion Commit information (source file changes and related comments) into our release notes file.
I couldn't yet figure out a way to access the Subversion Commit data from within the Jira export template.
Any ideas?
Thanks, Chris
Nov 06, 2005
Keith says:
Hi Chris, Glad to hear you are enjoying using the Subversion plugin. The best ...Hi Chris,
Glad to hear you are enjoying using the Subversion plugin.
The best place to see how this is done is within the Subversion source itself - available in the normal download on this page. From here, please take a look at:
../src/java/com/atlassian/jira/plugin/ext/subversion/issuetabpanels/changes/SubversionRevisionsTabPanel.java
../src/etc/templates/plugins/subversion/issuetabpanels/subversion-commits-view.vm
The basic operation is to pass the SubversionRevision object to the velocity template used for the release notes and then use it as in the subversion-commits-view.vm template.
The SubversionRevisionsTabPanel class encapsulates the logic used to retrieve the Subversion commits.
Let us know if you need any further information.
Regards,
Keith
May 29, 2007
Dmitry Taur says:
The basic operation is to pass the SubversionRevision object to the veloc...Could you please describe how it can be done in more details?
Thanks.
Nov 11, 2005
Anonymous says:
Is there a way to associate an already committed SVN change with a Jira issue? ...Is there a way to associate an already committed SVN change with a Jira issue?
Thanks
Martin
Nov 11, 2005
Jonathan Nolen says:
You can edit the commit message post-commit using Subversion. If you include the...You can edit the commit message post-commit using Subversion. If you include the issue number, JIRA will pick up the change the next time it parses the log.
Cheers,
Jonathan
Nov 14, 2005
Anonymous says:
Thank you for your response. I successfully modified the svn:log property on my ...Thank you for your response. I successfully modified the svn:log property on my file and added the missing reference to the Jira key but while the change is reflected in the SVN log as expected it had no effect on the referenced issue.
I used the following command:
$ svn propset --revprop -r 332193 svn:log -F 332193.log PATH
The SVN change and Jira issue are below. Do you have any idea what I might have done wrong?
http://svn.apache.org/viewcvs.cgi/incubator/stdcxx/trunk/tests/support/18.limits.traps.cpp?rev=332193&view=log http://issues.apache.org/jira/browse/STDCXX-4?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
Nov 14, 2005
Jonathan Nolen says:
The SVN plugin re-indexes the repository on a certain schedule – it's poss...The SVN plugin re-indexes the repository on a certain schedule – it's possible that this reindex hasn't happened yet. Wait 24 hours and see if the message appears. If not, let me know and I'll continue investigating.
Nov 16, 2005
Anonymous says:
Thanks, Jonathan. I'm afraid the commit is still not reflected in the issue toda...Thanks, Jonathan. I'm afraid the commit is still not reflected in the issue today.
Nov 16, 2005
Jonathan Nolen says:
OK, time to get more drastic. We can remove the Subversion indexes and force the...OK, time to get more drastic. We can remove the Subversion indexes and force the plugin to reindex all the commit messages.
Nov 16, 2005
Anonymous says:
Yikes! That does sound drastic I don't think I should do this to the Apache...Yikes! That does sound drastic
I don't think I should do this to the Apache Jira, but let me point the Jira admins to this thread to see if there's anything they can do.
Thanks for all your feedback!
Sep 28
Greg says:
We had to delete the atlassian-subversion-revisions folder to force complete rei...We had to delete the atlassian-subversion-revisions folder to force complete reindex. Our repository is quite large. How long does it take to reindex? Also I should note the reason we took this measure is because after adding a large number of files to the repository JIRA started running so slow that it wasn't usable. Note that we stopped the Apache-Tomcat server, deleted the indexing folder, restarted Apache-Tomcat.
1) Was the slow response due to the large import?
2) How will I know when the reindexing is completed?
3) Will the scheduled indexing interfere if a new schedule time comes up and the previous reindex was not complete?
Nov 15, 2005
Anonymous says:
Is there anything special to do to activate the display of the subversion tab. T...Is there anything special to do to activate the display of the subversion tab. The plugin seems properly installed and active (as per the UI).
But I cannot see it anywhere.
Nov 15, 2005
Anonymous says:
The "View Version Control" permission is needed - check http://www.atlassian.com...The "View Version Control" permission is needed - check http://www.atlassian.com/software/jira/docs/latest/permissions.html
Nov 16, 2005
Anonymous says:
It is set but the tab is still not showing up. I guess I will I have to turn on ...It is set but the tab is still not showing up. I guess I will I have to turn on some logging.
Nov 16, 2005
Anonymous says:
I added these two lines in my log4j.properties : log4j.category.com.atlassian.ji...I added these two lines in my log4j.properties :
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console, filelog
log4j.additivity.com.atlassian.jira.plugin.ext.subversion = false
Nothing shows up in the log.
The plugin shows up as active but the subversion still does not show up.
Weird!
Nov 16, 2005
Anton Mazkovoi says:
Hi, Could you please create a support request on http://support.atlassian.com ...Hi,
Could you please create a support request on http://support.atlassian.com and attahc your configuration files and logs. This way we should be of more help.
Cheers,
Anton
Nov 16, 2005
Anonymous says:
Is there any mechanism (e.g., a special keyword) that would cause the plugin to ...Is there any mechanism (e.g., a special keyword) that would cause the plugin to insert a hyperlink to an SVN revision when the revision number is mentioned in a changelog entry? For example, in the changelog text "see also revision #123456 for a similar fix" the "#123456" would be replaced by a viewcvs hyperlink to that revision.
Thanks
Martin
Nov 20, 2005
Anton Mazkovoi says:
Martin, Unfortunately this functionality is not available at the moment. I have...Martin,
Unfortunately this functionality is not available at the moment. I have created a feature request for this: http://jira.atlassian.com/browse/SVN-60
Please note that the source of the SVN plugin is available, so if you have the resource in house you can have a look at creating this functionality.
Dec 15, 2005
Anonymous says:
FYI This does not work with JavaSVN 1.0 .0 -- use the older ...FYI This does not work with JavaSVN 1.0 .0 -- use the older 8.8*
Dec 15, 2005
Keith says:
Thank you for the heads-up on this - we shall investigate this incompatibility a...Thank you for the heads-up on this - we shall investigate this incompatibility as and when we are looking at upgrading this dependency.
Jan 06, 2006
Anonymous says:
It is still the case that if you have even one commit in your SVN repository tha...It is still the case that if you have even one commit in your SVN repository that does not have an author it will fail to grab the log info (or behave oddly and get a subset of it). By default CVS2SVN does not put an author on its initial repository creation so this is a problem. If you use CVS2SVN specify a default author for the conversion and this problem can be avoided. If you have already converted you can use TortiseSVN to look at the full log and find the authorless commits and put an author on them (enabling the editinig requires a little config on your SVN repository but def worth it).
Jan 19, 2006
Jeff Huff says:
Is there a way to query the Subversion commits for a particular issue? I h...Is there a way to query the Subversion commits for a particular issue? I have started working with the Jira SOAP RPC client, but I have not figured out if the API can extend to plugins, or if a plugin has a way to expose its data to the RPC client.
In our current environment that we are looking to convert to from an existing system with customization to Subversion and Jira. We perform an "audit" of all defects in a particular state to verify that only changes that are in a particular defect state are part of release builds since the last "tagged" release. In order to do that, I need to be able to query all issues for a particular product and version (Jira speak) and are in a particular state. For each of those issues, I need to get the parts or files that are associated with the issue and update each file to the versions in the issue. This is so that files changed against issues that are not in a fixed or resolved state are not part of a release build.
I am not sure if this is a question for the Subversion plugin forum or the RPC plugin forum.
Jan 19, 2006
Jeff Turner says:
The SOAP API does not expose plugin info, but it is just a plugin, and you can c...The SOAP API does not expose plugin info, but it is just a plugin, and you can create your own SOAP endpoints that make this info available, and package them as a plugin:
http://confluence.atlassian.com/display/JIRA/RPC+Endpoint+Plugin+Module
If you have questions, the best place would be the jira-developer mailing list, linked from:
http://developer.atlassian.com
Cheers,
Jeff
Jan 26, 2006
Reid Maynard says:
Hi in the subversion-jira-plugin.properties file; svn.root=svn://........ &nbs...Hi
in the subversion-jira-plugin.properties file; svn.root=svn://........
Does this point to the directory HOLDING the individual repositories, or the individual respoitories?
Jan 29, 2006
Jeff Turner says:
It can point to either - any directory from the root down. Eg. if you only want ...It can point to either - any directory from the root down. Eg. if you only want the main trunk of project foo, it might be svn://localhost/repos/foo/trunk, or if you want everything, specify svn://localhost/repos/
Jan 26, 2006
John Kowalski says:
Please make your plugin compatible with the latest version of JavaSVN. Pretty pl...Please make your plugin compatible with the latest version of JavaSVN. Pretty please!! Subversion is 1.3 and only the latest version of JavaSVN (1.0.2) fully supports it.
Thanks
Jan 27, 2006
Jeff Turner says:
John, Do you have more information about this? Surely it doesn't matter what ve...John,
Do you have more information about this? Surely it doesn't matter what version the Subversion server is - old subversion clients (including older JavaSVNs) should still work. From the svn 1.3 release notes, "Older clients and servers interoperate transparently with 1.3 servers and clients." What problem are you experiencing?
Cheers,
Jeff
Jan 28, 2006
John Kowalski says:
Hi Jeff, This is what's stated on the Subversion site: Subversio...Hi Jeff,
This is what's stated on the Subversion site:
I haven't experienced any problems because I removed this plugin before I did run into anything. What's your take on this?
Thanks
Jan 29, 2006
Jeff Turner says:
Interesting, thanks. I suspect JIRA won't be affected by this change though, bec...Interesting, thanks. I suspect JIRA won't be affected by this change though, because it doesn't keep a local working copy of the module - it requests the logs directly.
Cheers,
Jeff
Jan 30, 2006
Chris Martino says:
How can I tell the plugin to use a different directory for .javasvn? I'm r...How can I tell the plugin to use a different directory for .javasvn? I'm running Jira (and the plugin) in a diskless environment and it keeps on trying to put it's logfile in /.javasvn. / is a read-only filesystem. I've tried setting $HOME before launching Jira, but that doesn't appear to solve any problems. Thanks!
Jan 31, 2006
Dylan Etkin says:
Hi Chris, It is actually the javasvn library that the subversion plugin uses whi...Hi Chris,
It is actually the javasvn library that the subversion plugin uses which is generating that log file. You can disable its file logging by providing the -Djavasvn.log.file=false parameter to the java command-line that starts your JIRA instance. We are using version 0.8.8 of javasvn and this will work with this version. Apparently it is disabled by default in the 1.x versions.
I hope that helps,
Dylan
Feb 01, 2006
Reid Maynard says:
Hi Running jira 3.4.3/plugin 0.8.x it seems some Jira projects provide the Sub...Hi
Running jira 3.4.3/plugin 0.8.x
it seems some Jira projects provide the Subversion Commits tab just fine; others fail .. I get this in the catalina.out:
2006-02-01 09:43:56,237 WARN [web.action.issue.ViewIssue] Unknown tab panel 'com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel' has been specified.
-Reid
Feb 01, 2006
Dylan Etkin says:
Hi Reid, That sounds strange. Could you open a support request about this at ht...Hi Reid,
That sounds strange. Could you open a support request about this at https://support.atlassian.com and include your subversion-jira-plugin.properties file, your complete JIRA log, and any other data you may feel is relevant.
Thanks,
Dylan
Feb 17, 2006
Jeff Huff says:
I noticed an issue with the way that one of the issue links is rendered in the S...I noticed an issue with the way that one of the issue links is rendered in the Subversion Commits tab.
The velocity template for the commits tab has a section like this...
<tr>
<td bgcolor="#f0f0f0" width=10%><b>Repository</b></td>
<td bgcolor="#f0f0f0" width=10%><b>Revision</b></td>
<td bgcolor="#f0f0f0" width=10%><b>Date</b></td>
<td bgcolor="#f0f0f0" width=10%><b>User</b></td>
<td bgcolor="#f0f0f0"><b>Message</b></td>
</tr>
<tr>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>$action.repositoryDisplayName</td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>$action.linkRenderer.getRevisionLink($action.revision)</td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>$!action.revision.date</td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>$!action.revision.author</td>
<td bgcolor="#ffffff">#makelinkedhtml($action.revision.getMessage().trim())</td>
</tr>
is rendered as... <tr>
<td bgcolor="#f0f0f0" width=10%><b>Repository</b></td>
<td bgcolor="#f0f0f0" width=10%><b>Revision</b></td>
<td bgcolor="#f0f0f0" width=10%><b>Date</b></td>
<td bgcolor="#f0f0f0" width=10%><b>User</b></td>
<td bgcolor="#f0f0f0"><b>Message</b></td>
</tr>
<tr>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>Development</td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3><a href="http://svn/wsvn/Dev/?rev=7&sc=1">#7</a></td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>Fri Feb 17 16:03:33 MST 2006</td>
<td bgcolor="#ffffff" width=10% valign=top rowspan=3>jhuff</td>
<td bgcolor="#ffffff"> Issue:<a href="http://issues/jira/browse/TST-5" title="Test bug issue"><strike>TST-5</strike></a>;Test message
</td>
</tr>
The <strike>TST-5</strike> does what you would expect and strikes through the TST-5 in the link text. Is there a reason that it puts strike around the issue link text?
Thanks in advance.
Feb 20, 2006
Dylan Etkin says:
Hi Jeff, The strike is meant to indicate that the issue is currently resolved. ...Hi Jeff,
The strike is meant to indicate that the issue is currently resolved. Open issues should not have the strike tags.
Dylan
Apr 05, 2006
Matt Klaustermeier says:
Dylan, Is there a way turn off the "strike" tag when showing links to JIRA issu...Dylan,
Is there a way turn off the "strike" tag when showing links to JIRA issues in the Subversion tab? For our particular situation, the Subversion commit is done around the time that the issue is resolved, meaning that the JIRA issue links almost always have a strike through them, making them harder to read.
After glancing through the code, if I'm following it correctly, it appears to be using capabilities built into JIRA to do this, so it's possible that I should be trying to figure out how to turn this off in JIRA as opposed to just the Subversion plugin, but I thought I'd just start here since I saw this posting.
Thanks in advance,
Matt
Apr 09, 2006
Brian Nguyen says:
Hi Matt, I'll jump in for Dylan here. The strike tag that is added, is part of...Hi Matt,
I'll jump in for Dylan here.
The strike tag that is added, is part of a method within Jira that creates links to other issues. So this is piece of code is also used in comments, and descriptions, and, unfortunately, in order to turn this off you will need to edit the source directly.
So to do this:
If you need any help with this, please feel free to submit a support request at https://support.atlassian.com or post a question to our user/developer lists.
Thanks,
Brian
Apr 10, 2006
Matt Klaustermeier says:
That's exactly what I was looking for. I searched and searched for this earlier....That's exactly what I was looking for. I searched and searched for this earlier... I don't know why I couldn't find it.
Thanks!!
Mar 02, 2006
Reid Maynard says:
hi I have two subversion servers accessed via the plugin, about 50 repos ...hi
I have two subversion servers accessed via the plugin, about 50 repos on each server. But now starting JIRA seems to take much longer; is it now logging into each repo durring startup?
Mar 02, 2006
Dylan Etkin says:
Hi Reid, When you startup JIRA the service which updates the subversion indexes...Hi Reid,
When you startup JIRA the service which updates the subversion indexes does run, but it should be running in a different thread than the main process. That said, I imagine it is doing quite a bit of work so this would probably slow everything down. If it is very slow then I would suggest opening a support request about it.
Thanks,
Dylan
Apr 27, 2006
Reinhard Brandstädter says:
Running the Plugin Version 0.9.2 with JIRA 3.5.1 doesn't work (using the 0.9.1 p...Running the Plugin Version 0.9.2 with JIRA 3.5.1 doesn't work (using the 0.9.1 plugin and the same configuration works fine).
The JIRA log shows this exceptions:
2006-04-27 13:16:05,724 ERROR [ext.subversion.revisions.RevisionIndexer] Could not load properties from subversion-jira-plugin.properties
java.lang.NoSuchMethodError: com.atlassian.jira.service.ServiceManager.getServiceWithName(Ljava/lang/String;)Lcom/atlassian/jira/service/JiraServiceContainer;
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.install(RevisionIndexService.java:49)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:67)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:205)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:318)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:246)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
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.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1567)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:482)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:968)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
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.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
2006-04-27 13:16:05,727 ERROR [com.atlassian.jira.ComponentManager] Error occurred while starting component.
com.atlassian.jira.InfrastructureException: Could not load properties from subversion-jira-plugin.properties
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:72)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:205)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:318)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:246)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
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.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1567)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:482)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:968)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
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.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
May 01, 2006
Jeff Turner says:
I've added a version compatibility table to make it clear what is compatible wit...I've added a version compatibility table to make it clear what is compatible with each JIRA version.
May 04, 2006
Richard Kroll says:
Is there a way to create a link to the brang / tag when displaying which files w...Is there a way to create a link to the brang / tag when displaying which files were affected by the commit? For us it would be perfect if it listed in addition to the repository and revision, either /trunk/ or the tag/branch the change belonged to.
May 09, 2006
Keith says:
Hi Richard, Apologies for the delay in responding. Can you explain your setup ...Hi Richard,
Apologies for the delay in responding.
Can you explain your setup a little further? Do you have the JIRA Subversion plugin pointing at trunk/ or do you have it pointing to the root of your subversion repository? If it is pointing at the root, does the link to the changed file include the tag/branch also?
Also, if a file has been copied (branched) - the plugin should display the link to where it was copied from and what revision the origin path was at.
Regards,
Keith
May 15, 2006
Roger Yang says:
Dear sirs : Is there a feature that can let JIRA send out the email to no...Dear sirs :
Is there a feature that can let JIRA send out the email to notify target users when I commit/update files at subversion?
thanks a lot.
May 16, 2006
Justin Koke says:
Hi Roger, I think what you really want is something that hook directly into Sub...Hi Roger,
I think what you really want is something that hook directly into Subversion. I would suggest something like svnmailer
Cheers,
Justin
May 17, 2006
Joe Shomphe says:
Is there any way to make the indexing of jira issues case insensitive? We ...Is there any way to make the indexing of jira issues case insensitive? We have some users who seem to always add our issues as project-1 rather than PROJECT-1.
I guess this could be fixed with a commit hook also that checked for a valid jira issue.
Any suggestions?
May 19, 2006
Dylan Etkin says:
Hi Joe, I have raised an issue about this here, http://jira.atlassian.com/brows...Hi Joe,
I have raised an issue about this here, http://jira.atlassian.com/browse/SVN-93. We should fix this up.
Thanks,
Dylan
Jul 20, 2006
Dan D'Eramo says:
I just installed the Subversion plugin 0.9.4 into JIRA 3.6.2, but on the 'Admini...I just installed the Subversion plugin 0.9.4 into JIRA 3.6.2, but on the 'Administration > Plugins' page it is listed as 'Plugin Version: 0.9.2'.
What are all of the linkformat.* properties for? Do at least one of the ViewCVS / ViewSVN / Fisheye / TortoiseSVN groups have to be set up? Can more than one be set up?
Thanks,
Dan
Jul 24, 2006
Justin Koke says:
Hi Dan, Thankyou for the note regarding the 0.9.4 / 0.9.2 problem. This was sim...Hi Dan,
Thankyou for the note regarding the 0.9.4 / 0.9.2 problem. This was simply an error and can be ignored. I have re-versioned the plugin so the version is now correct.
The linkformat properties are used when the plugin renders the change logs, it is possible to click on the changed files and view them in ViewCVS etc.
Yes more than one repository can be setup, but there is a one-to-one mapping between a repository and link format.
I hope this helps answer your questions.
Cheers,
Justin
Jul 27, 2006
Adam Gentry says:
We currently use tortoiseSVN and I was wondering if there is any work out there ...We currently use tortoiseSVN and I was wondering if there is any work out there that will allow a developer to select in a drop down the tasks/defects in a JIRA project from the commit window?
Regards,
Adam
Aug 01, 2006
Justin Koke says:
Hi Adam, Looking through the TortoiseSVN doco I found the following documentati...Hi Adam,
Looking through the TortoiseSVN doco I found the following documentation that should provide what you need:
http://www.tortoisesvn.net/docs/release/TortoiseSVN_en/ch05s24.html
Regards,
Justin
Jul 28, 2006
Chris B. says:
Hi, Jira and Subversion runs on the same server. The plugin works but with Auth...Hi,
Jira and Subversion runs on the same server. The plugin works but with Auth fail exception.
How can i configurate the plugin, that the ssh key it found? Because we use key's and not password.
tHx
Chriz
Aug 01, 2006
Jeff Turner says:
Chris, There is a patch available which adds support for public key authenticat...Chris,
There is a patch available which adds support for public key authentication:
http://jira.atlassian.com/browse/SVN-95
We have not yet had a chance to test it.
Cheers,
Jeff
Aug 03, 2006
Chris B. says:
hi jeff, we run JIRA 3.4.1 and the subversion plugin 0.8.2. are for this ...hi jeff,
we run JIRA 3.4.1 and the subversion plugin 0.8.2. are for this version also an patch available?
thX
chris
Aug 03, 2006
Jeff Turner says:
No, but as it's a patch it should be fairly easy to apply by hand to earlier sou...No, but as it's a patch it should be fairly easy to apply by hand to earlier source releases.
Aug 02, 2006
Paul Dale says:
Hello, I've been trying to get this plugin to work (0.9.4) with jira-standard-3...Hello,
I've been trying to get this plugin to work (0.9.4) with jira-standard-3.6.2
I keep getting something like the following bit. Seems to be something wrong with subversion-jira-plugin.properties, but I can't tell what its upset about.
My subverison-jira.plugin.properties is in the WEB-INF/classes directory and contains the lines
svn.root=svn://tps:6969/tools/bk
svn.display.name=BKRepository
svn.password=pw
revision.cache.size=10000
Any suggestions as to what is wrong?
Thanks!
Paul
2006-08-02 15:24:58,940 INFO [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] No svn.root.1 specified in subversion-jira-plugin.properties
2006-08-02 15:24:58,940 INFO [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] No svn.root.1 specified in subversion-jira-plugin.properties
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:56)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:30)
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:494)
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 com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:315)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:252)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4104)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
2006-08-02 15:24:58,968 ERROR [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] Could not load properties from subversion-jira-plugin.properties
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:56)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:30)
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:494)
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 com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:315)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:252)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4104)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
2006-08-02 15:24:58,968 ERROR [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] Could not load properties from subversion-jira-plugin.properties
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:56)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:30)
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:494)
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 com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:315)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:252)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4104)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
2006-08-02 15:24:58,977 ERROR [ContainerBase.[Catalina].[localhost].[/]] Exception sending context initialized event to listener instance of class com.atlassian.jira.upgrade.ConsistencyLauncher
com.atlassian.jira.InfrastructureException: Could not load properties from subversion-jira-plugin.properties
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:85)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:30)
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:494)
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 com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:315)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:252)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:25)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4104)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
Caused by: java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:56)
... 31 more
Aug 2, 2006 3:25:00 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Aug 2, 2006 3:25:00 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors
2006-08-02 15:25:00,210 ERROR [org.quartz.core.QuartzSchedulerThread] releaseTriggerRetryLoop: RuntimeException null
java.lang.NullPointerException
at com.atlassian.scheduler.OfBizJobStore.releaseAcquiredTrigger(OfBizJobStore.java:516)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:281)
Aug 02, 2006
Terry Ooi says:
Hi Paul, It seems like JIRA can't locate the subversion-jira-plugin.properties....Hi Paul,
It seems like JIRA can't locate the subversion-jira-plugin.properties. Are you using JIRA WAR installation? If that is the case, you should put subversion-jira-plugin.properties into edit-webapp/WEB-INF/classes and rebuild the WAR file.
If the problem still persists, I would recommend you to raise a support request at http://support.atlassian.com and attach your log file. We will love to get to the bottom of your problem.
Cheers,
Terry
Aug 03, 2006
Paul Dale says:
Well, it seems to me that it is finding the subversion-jira-plugin.properties fi...Well, it seems to me that it is finding the subversion-jira-plugin.properties file. As when I change the values inside the error message changes. Note the first two lines;
No svn.root.1 specified in subversion-jira-plugin.properties
If I put a svn.root.1 in, then it says svn.root.2, etc
Will post the file to support.
Thanks,
Paul
Aug 06, 2006
Dave M says:
i know i'm missing something, but can't seem to find what i am looking for. &nb...i know i'm missing something, but can't seem to find what i am looking for.
jira says the plugin is working.
i created a project.
am i supposed to create a new cvs module and just use the suversion information? if so, what do i use for the log file path? i'm kind of new to both jira and subversion, so i'm not quite sure where subversion keeps its log files.
if not, i don't see a "add svn module" link.
Aug 06, 2006
Jeff Turner says:
You can completely ignore the CVS Modules section of the admin screen. It is for...You can completely ignore the CVS Modules section of the admin screen. It is for CVS, not Subversion.
All you really need is:
The Subversion plugin will obtain logs itself when it connects.
It would be a good idea to first try connecting to your Subversion server with something like TortoiseSVN. Try checking out a module. Then commit a change, and in the commit comment, mention a JIRA issue key. Then once you hook JIRA up to it, you should see a Subversion tab for that issue.
If you have problems, feel free to raise a support request at https://support.atlassian.com, attaching your properties config file.
Cheers,
Jeff
Aug 21, 2006
Dave M says:
wonderfully helpful. looks like its functioning properly. thanks a ton. _dwonderfully helpful. looks like its functioning properly. thanks a ton.
_d
Sep 11, 2006
Emily Stumpf says:
Hello, At the moment I see that the subversion plugin is installed (Admin->P...Hello,
At the moment I see that the subversion plugin is installed (Admin->Plugins), but I do not see any tabs anywhere, or anything for Subversion listed under Admin->Services. Now, I did have a typo in the name of the first repository in my subversion-jira-plugin.properties, and a a couple of permissions errors that I can't fix until I'm allowed to redeploy.. But I was just wondering if I should still have the Service and/or the Tabs.
Thanks!
-- Emily
Sep 12, 2006
Dylan Etkin says:
Hi Emily, You don't have to worry about it. The plugin is smart enough so that ...Hi Emily,
You don't have to worry about it. The plugin is smart enough so that if it is unable to properly initialize itself then the tab panel does not show and the service is not registered. Once you correct the errors in your properties file and the plugin can connect to the svn server you should see the tab panel.
I hope this helps,
Dylan
Sep 28, 2006
Kertes Gábor says:
Is there a way to temper with some regular expressions in the plugin's configura...Is there a way to temper with some regular expressions in the plugin's configuration so that it recognizes commit comments with various JIRA issues like PRJ-1,2,4 (i.e.: PRJ-1, PRJ-2, PRJ-4), as commits related to multiple jira issues?
I use the following SVN properties:
bugtraq:label=Jira Issue: PRJ-
bugtraq:url=http://domain.com/browse/PRJ-%BUGID%
bugtraq:message=Jira Issue: PRJ-%BUGID%
bugtraq:append=false
bugtraq:number=true
bugtraq:warnifnoissue=true
bugtraq:logregex=
PRJ-(\d+)(,'(\d+))+
(\d+)
And without using precommit hooks this leaves me with commit comments like: PRJ-2,3,4 and commits linked -- in this particular case -- to PRJ-2 issue only. The developers are lazy, they don't want to type the project prefix for every issue.
Any ideas how to deal with this situation?
K>
Oct 02, 2006
Justin Koke says:
Hi Kertes, I would suggest going to the TortoiseSVN mailing list and asking thi...Hi Kertes,
I would suggest going to the TortoiseSVN mailing list and asking this question there: http://tortoisesvn.net/support.
Since the configuration questions you are asking are for the TortoiseSVN client and not the JIRA SVN plugin.
From what I am gathering what you are after is a search and replace of the log message for any matches on this PRJ-1,2,3 and creating a log message that looks like: PRJ-1,PRJ-2,PRJ-3.
From reading the article here: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/ch05s24.html I am a little unclear if the logregex property actually can perform an actual search and replace, or if it simply matches the regex groups (which is what I think you are after).
Regards,
Justin
Oct 09, 2006
Kertes Gábor says:
Thanks, Justin. These aren't Tortoise specific properties, other clients, like s...Thanks, Justin. These aren't Tortoise specific properties, other clients, like subclipse, recognize them as well.
My problem is that while Subclipse, for example, parses and matches PRJ-1,2,3 from the commit comment as three links to three issues, the JIRA Subversion plugin matches only PRJ-1, not 2 and 3.
I don't want to replace anything in the log message (bugtraq:logregex won't do that, though I admit, its description is quite confusing), at least I don't want to use svn-hook scripts (and I think I should have to, to replace 'PRJ-1,2,3' to 'PRJ-1, PRJ-2, PRJ-3'). My question was if I was able to change how pattern matching works in the JIRA Subversion plugin. Actually, it would be a nice feature if the plugin used the the bugtraq:logregex property (to find issue numbers), if present.
Thanks for your time,
K>
Oct 12, 2006
Justin Koke says:
Hi Kertes, To look at this regex to be changed it would actually be a change to...Hi Kertes,
To look at this regex to be changed it would actually be a change to Jira source (at the moment), since the Velocity template used by the plugin relies on the velocity macro used in other areas of JIRA (shuch as what you see when you use an issue key in a comment).
If this was to be changed you would need to look at making the call #makelinkedhtml call a different version of com.atlassian.jira.util.JiraKeyUtils that has a different regex. Currently the regex is '/(^|[^a-zA-Z]|\n)([A-Z][A-Z]-[0-9])/' so this would need to have an added comma grouping to manage the issue links you suggest.
So if you wish to change this, you would need to patch the class I mentioned.
Regards,
Justin
Oct 16, 2006
Kertes Gábor says:
Thank you, Justin. K>Thank you, Justin.
K>
Oct 01, 2006
Vairoj Arunyaangkul says:
Does the current version of this plugin (0.9.4) supports connecting with Subvers...Does the current version of this plugin (0.9.4) supports connecting with Subversion 1.4 server? If not, what is the timeframe for the supported version? I am planning on upgrade the whole SVN environment in my company to v.1.4 and would like to make sure that nothing will break.
Oct 02, 2006
Justin Koke says:
Hi, Since this plugin uses JavaSVN, support for 1.4 is reliant on when JavaSVN ...Hi,
Since this plugin uses JavaSVN, support for 1.4 is reliant on when JavaSVN fully supports 1.4. From looking at their mailing list http://www.nabble.com/JavaSVN-f10898.html this will be when 1.1.0 is fully released (they are currently in 'beta4').
Have you tried pointing the plugin against 1.4? We currently test this plugin against svn 1.3.2
Regards,
Justin.
Oct 04, 2006
Brian Fox says:
I use this against svn 1.4 with no problems. The network api is backwards compat...I use this against svn 1.4 with no problems. The network api is backwards compatible with the older clients so it's not an issue. The main incompatibility is in repository tools (maybe if you use file://) and with clients and their working folder. I'm using http/https with no problems.
Dec 27, 2006
Jerry Brown says:
I see that JavaSVN has experienced a name change concurrent with the 1.1.0 relea...I see that JavaSVN has experienced a name change concurrent with the 1.1.0 release. Info is http://svnkit.com/. This version has complete support for Subversion 1.4.2.
Any likelihood of an update to this plugin to pick up the JavaSVN/SVNKit update?
Dec 27, 2006
Jeff Turner says:
Raised as http://jira.atlassian.com/browse/SVN-120Raised as http://jira.atlassian.com/browse/SVN-120
Jan 30, 2007
Lehky, Miro says:
Any update on support for SVNKit. We tried using JavaSVN with Subversion ...Any update on support for SVNKit.
We tried using JavaSVN with Subversion 1.4.x and it was not pretty, lots of connection errors and such. Now that we've migrated to SVN (from CVS), I'd like to try out this plugin, but with past experinece with JavaSVN I'm very reluctant.
Miro
Jan 30, 2007
Dylan Etkin says:
It is not in the current roadmap for 3.8 things to do, but we will take a look a...It is not in the current roadmap for 3.8 things to do, but we will take a look at it when we can. Sorry for the lack of an answer.
Oct 09, 2006
John Ski says:
Hi, Just upgraded to JIRA 3.6.5 and the 0.9.4 Sub Plugin and I'm having a few i...Hi,
Just upgraded to JIRA 3.6.5 and the 0.9.4 Sub Plugin and I'm having a few issues with the plug-in. I was running 3.3.2 JIRA with the 0.7.1 SVN plug-in and everything worked perfectly for over a year!
First up... I have 2 repos on the same host. I had to add a "svn://" to the svn.root.1= so the plug-in would find the second repo.
In 0.7.1 the second repo was defined as "svn.root.1=//localhost/documentation" This worked fine, but in 3.6.5/0.9.4 it threw this error:
2006-10-08 15:28:35,292 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository //localhost/documentation failed: org.tmatesoft.svn.core.SVNException: svn: Malformed URL '//localhost/documentation'
org.tmatesoft.svn.core.SVNException: svn: Malformed URL '//localhost/documentation'
Changing the svn.root.1=*svn://*localhost/documentation seemed to correct the above error in 0.9.4 but I'm not seeing the commit changes... This may be due to the next error....
Second.. I'm getting the following error on my primary repo and no index files are created. The Subversion Commit tab exists but nothing is showing on the tab. Also, no index files are being created in the plug-in index path.
2006-10-09 08:19:16,001 ERROR [ext.subversion.revisions.RevisionIndexService] Error indexing changes: org.tmatesoft.svn.core.SVNException: svn: File not found: revision 12213, path '/development'
org.tmatesoft.svn.core.SVNException: svn: File not found: revision 12213, path '/development'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:43)
at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:281)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:196)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:916)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.log(SVNRepositoryImpl.java:501)
at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:629)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateIndex(RevisionIndexer.java:252)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.run(RevisionIndexService.java:29)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
The revision listed in the error message is the latest revison number in the repo. As new revisions are added to SVN, the revision number in the error message increase. It always fails on the current (HEAD) revison number.
Subverion was not changed. It's still 1.2.3 and the repos are exactly as they were prior to the upgrade. It's NOT a permission issue. Everything is defined as it was, and the Subversion Commit tab is displayed with the standard message "There are no subversion log entries for this issue yet."
I have not tried a previous version of the sub plug-in. Any ideas would be appreciated at this point!
Thanks!
-John
Oct 09, 2006
John Ski says:
Update! I changed the svn.root= (both root= and root.1=) to http: in place ...Update!
I changed the svn.root= (both root= and root.1=) to http: in place of svn: and it's working now. I run both http:// and svn :// services (Apache2/DAV/SSPI and SVNserve read-only) for Sub access. svn:// is MUCH faster when you only need to read from SVN.
I tested the URL via svn:// (Eclipse3.2 with Subclipse) and it works fine. I'm going to check a few more things with the SVNServer.
-John
Oct 11, 2006
Jeff Turner says:
> org.tmatesoft.svn.core.SVNException: svn: File not found: revision 12213, p...> org.tmatesoft.svn.core.SVNException: svn: File not found: revision 12213, path '/development'
That sounds like an error on the repository. Perhaps try 'svn log svn://localhost/documentation'. If that works, then so should JIRA.
Nov 21, 2006
Amos Hayes says:
FYI. When using an HTTPS repository with a cacert.org or self-signed cert, I was...FYI. When using an HTTPS repository with a cacert.org or self-signed cert, I was receiving an authentication error in the catalina.out log from the subversion plug-in. Jira would load, the plug-in would appear to be running in the list, but no subversion tab was present in issues.
After running svn list on the repository as the application server (tomcat) user and accepting the cert permanently, the subversion plug-in was able to connect and began working as advertised.
The error messages seemed to imply that it had something to do with the username or password being used. There was no hint that it might be a cert trust issue.
Nov 21, 2006
Jeff Turner says:
Thanks for the note. Connecting to HTTPS services, I imagine you'd need to pre-a...Thanks for the note. Connecting to HTTPS services, I imagine you'd need to pre-approve the SSL certificate, by importing it into the Java truststore:
http://confluence.atlassian.com/display/JIRA/Connecting+to+SSL+services
Feb 01, 2008
Igor Muratov says:
Please, remove my messagePlease, remove my message
Dec 13, 2006
Clint Hanson says:
Ok this is in regards to using multiple repositories and websvn. I modifie...Ok this is in regards to using multiple repositories and websvn. I modified the ViewCVSLinkRenderer file to allow me to add an entry in the subversion-jira-plugin.properties file of the type:
${repo}Since I didn't want to change the structure of the properties file I set it so that anywhere
${repo}is found in the link format entries in the properties file it will replace it with the svn.display.name entry for each of your repositories.
So for example:
By entering in an entry such as
linkformat.changeset=https://xxx.xxx.xxx.xxx/${repo}viewcvs?view=rev&rev=${rev}Will replace
${repo}with each entry for the appropriate repository.
Is there any interest from others who would like this functionality? Now we should be able to build the strings needed for whatever display mechanism you wish to use. Using websvn and multiple repositories on RedHat linux, and RHEL4 not having the necessary rpms needed to install ViewVC it wasn't worth it for me to invest the time to recompile. Anyways this solution may help others. I can attach the code or send it to the maintainers of the plugin if they would like to use it, just let me know where I need to go from here.
PS I couldn't get the plugin environment working with Maven and everything else so I just built an Ant build script. The instructions for building and integrating a plugin need to either state that maven 2.0 won't work or there needs some specific configuration options for the maven build.
Mar 26, 2007
Jean-Francois Allot says:
Hi Clint, I am also using several SVN repositories and such keyword would reall...Hi Clint,
I am also using several SVN repositories and such keyword would really be helpful!
If the plugin authors would accept integrating your changes, it would really be fine.
Thank you for this!
Apr 02, 2007
Jeff Turner says:
Sounds neat. If you could generate a diff against svn and attach it to http://ji...Sounds neat. If you could generate a diff against svn and attach it to http://jira.atlassian.com/browse/SVN-131 we'll take a look at integrating it.
May 01, 2007
Owen Carter says:
Clint; Another 'ooh! yes please!' vote from me; this would be very useful in ou...Clint;
Another 'ooh! yes please!' vote from me; this would be very useful in our environment.
Nice work! Thanks; Owen.
Jul 09, 2007
Clint Hanson says:
Ok so I finally checked back here when upgrading to latest version of Jira. ...Ok so I finally checked back here when upgrading to latest version of Jira. Was very cool to see that an issue had been created! I have uploaded the patch to the Jira issue, and commented on it there. If anyone wants it they can go get it from the Jira issue linked in one of the replies.
I still can't get maven working as it is direct from the repository though with eclipse which is a bit annoying. Anyone got a good place to look up how to use this project in eclipse?
Jan 16, 2007
Wojciech Seliga says:
Hi, I have a strange problem with upgrading to JIRA 3.7.1. Using exactly the sa...Hi,
I have a strange problem with upgrading to JIRA 3.7.1. Using exactly the same plugin property file (but newest jar 0.9.6), during initialization of JIRA I receive the following exception:
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:57)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:31)
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:494)
at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:100)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:200)
...
2007-01-16 15:54:46,347 ERROR [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] Could not load properties from subversion-jira-plugin.properties
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.setupEnvironment(MultipleSubversionRepositoryManagerImpl.java:57)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:31)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
...
And whole JIRA ceases to continue startup :-(
Am I missing something? If I remove from war file subversion plugin jar, then everything works OK, so this is I think a problem related to this plugin.
Any ideas?
Thanks in advance.
Jan 17, 2007
Dylan Etkin says:
Hi Wojciech, I have been able to setup the subversion plugin against 3.7.x with...Hi Wojciech,
I have been able to setup the subversion plugin against 3.7.x without issue. Looking at the code it would seem that either the plugin is unable to get either the UUID or the Location from the subversion repository (unless you are seeing a message like: Connection to Subversion repository SVN_ROOT_HERE failed:, in your logs before this message).
If the tips above don't lead you to a solution I would suggest opening a support request at https://support.atlassian.com. Attaching your log and configuration files and relaying all the information about your environment would help us get to the bottom of the problem.
Thanks,
Dylan
Feb 02, 2007
Wojciech Seliga says:
Thanks for your answer. After a few days, I tried one more time (with the newest...Thanks for your answer. After a few days, I tried one more time (with the newest version 0.9.7, but without any changes to our JIRA configuration) and this time it worked without any problems...
Strange, but maybe I was doing something wrong.
Sorry for disturbing you.
Wojtek
Jan 17, 2007
Markus Nospers says:
Hi, are there any major issues why we should not use 0.9.6 with Jira 3.6....Hi,
are there any major issues why we should not use 0.9.6 with Jira 3.6.x?
We're running v3.6.3 currently but would like to get the nice project tab feature.
Regards
Markus
Jan 17, 2007
Dylan Etkin says:
Hi Markus, You should not use the 0.9.6 plugin with versions prior to 3.7 since...Hi Markus,
You should not use the 0.9.6 plugin with versions prior to 3.7 since we have changed the way that the issue tab panels work in 3.7, thus the subversion plugins issue tab panel has changed and will not be compatible with previous JIRA version.
Thanks,
Dylan
Jan 30, 2007
Dylan Etkin says:
I have raised an Improvement request about this here, http://jira.atlassian.com/...I have raised an Improvement request about this here, http://jira.atlassian.com/browse/SVN-127.
Jan 30, 2007
Panu Outinen says:
Hi! Is there a reason why 0.9.6 plugin is compiled with JDK 1.5's new features:...Hi!
Is there a reason why 0.9.6 plugin is compiled with JDK 1.5's new features:
...
Caused by: java.lang.UnsupportedClassVersionError: com/atlassian/jira/plugin/ext/subversion/issuetabpanels/changes/SubversionRevisionsTabPanel (Unsupported major.minor version 49.0)
...
Thanks,
PS. 0.9.5 plugin works fine with my old 1.4.1_0x debug environment
Feb 14, 2007
Chris Houghten says:
DITTO! This is the second plugin I have come across that has 1.5 code in it...DITTO!
This is the second plugin I have come across that has 1.5 code in it. Please stop coding for a jdk higher than is required by the core application!
Feb 14, 2007
Chris Houghten says:
My apologies.. I had some weirdness on my system that was causing this to compil...My apologies.. I had some weirdness on my system that was causing this to compile with 1.5. I did indee run into another plugin that did have 1.5 specific code and just jumped to the conclusion that this was the case here as well.
Feb 23, 2007
Adrian Bridgett says:
I've just upgraded jira from 3.6.4 to 3.7.3 and the whole "all/comments/subversi...I've just upgraded jira from 3.6.4 to 3.7.3 and the whole "all/comments/subversion" section disappeared from our jira installation. At first I thought it was the newly installed edit-comments plugin, but eventually tried upgrading this subversion plugin from 0.9.4 to 0.9.8 and this fixed the problem.
Thought this might be useful info for someone.
Mar 20, 2007
Thomas Poersch says:
Is it possible to set an issue's status automatically to FIXED when a commit is ...Is it possible to set an issue's status automatically to FIXED when a commit is executed?
I did not find any information about that.
Mar 20, 2007
Roman Kayrez says:
Is it possible to use this plugin through a proxy? I pass -Dhttp.proxyHost=a...Is it possible to use this plugin through a proxy? I pass -Dhttp.proxyHost=and the HTTP_PROXY environmenr variable is set, yet jira still gives this exception:
ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository failed: org.tmatesoft.svn.core.SVNException: svn: PROPFIND request failed on 'reponame'
svn: No route to host
org.tmatesoft.svn.core.SVNException: svn: PROPFIND request failed on 'reponame'
svn: No route to host
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:43)
at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:124)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.fetchRepositoryUUID(DAVConnection.java:92)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:76)
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.setupEnvironment(SubversionManagerImpl.java:96)
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.(SubversionManagerImpl.java:39)
(and so on...)
Mar 21, 2007
Roman Kayrez says:
Ah, I've figured it out: The svn proxy settings (http-proxy-host and http-proxy-...Ah, I've figured it out: The svn proxy settings (http-proxy-host and http-proxy-port) need to go into the ~/.subversion/servers file for the user under which tomcat runs.
Mar 26, 2007
Jean-Francois Allot says:
Hi, First, congratulations for this great plugIn which really leverages the val...Hi,
First, congratulations for this great plugIn which really leverages the value of Jira.
Would it be possible, in this page, to add a few more details about how the indexing works: full or incremental reindexing? Are the issue keys case sensitives? Is the edition of an existing log taking into account by the plugIn (if not full reindexing).
I've got most of the answers by looking at the code, but some few notes about this will help others when deplying such plugIn.
Thx.
Apr 04, 2007
Thomas Jenny says:
thanks for a great plugin. A small contribution: we are using sventon as a sub...thanks for a great plugin.
A small contribution:
we are using sventon as a subversion repo browser (alternative to FishEye, ViewSVN, ...). If you want to use this as well, the properties for your config file might look like the following:
#--------------------------------- # Sventon http://www.sventon.org #--------------------------------- #linkformat.changeset=http://your.host.address/svn/revinfo.svn?revision=${rev}&name=repo-name #linkformat.file.added=http://your.host.address/svn/showfile.svn?path=${path}&revision=${rev}&name=repo-name #linkformat.file.modified=http://your.host.address/svn/diffprev.svn?path=${path}&revision=${rev}&commitrev=${rev}&name=repo-name #linkformat.file.replaced=http://your.host.address/svn/showfile.svn?path=${path}&revision=${rev}&name=repo-name #linkformat.file.deleted=http://your.host.address/svn/showfile.svn?path=${path}&revision=${rev-1}&name=repo-name #linkformat.copyfrom=http://your.host.address/svn/showfile.svn?path=${path}&revision=${rev-1}&name=repo-name # #linkformat.changeset.1=... #linkformat.file.added.1=...Enjoy.
May 01, 2007
Owen Carter says:
Hi Tomas; very useful. I also found it useful to add the Sventon URL to the 'Su...Hi Tomas; very useful.
I also found it useful to add the Sventon URL to the 'Subversion repository display name' definition like this:
Owen.
PS: I've asked the Sventon list if it is possible to go between arbitrary revisions with the showdiff.svn url's; just diffprev.svn is, by nature, only going to the immediate previous revision and it may be desirable in the future to show the 'total' changes to a file (for instance, if a developer checks it in several time while working on the same issue.).
Apr 01, 2009
Ros Archer says:
Hi Thomas, thanks for your list of linkformats. I'm in the process of evaluati...Hi Thomas,
thanks for your list of linkformats. I'm in the process of evaluating Subversion Web Clients, so I'm checking out how easy it is to link them in with Jira. Might be worth requesting that these get added into the plugin baseline like those for WebClient for SVN were. It will make it easier for other users to determine which clients are going to integrate with this plugin.
In response to Owen's comment about viewing Diffs of versions other than the the previous version, I had a play with the demo Sventon repository, and was able to get arbitrary version diffs from the log file of a given file. I took note of the URL used to create the resulting page, and it looks like this:
http://svn.sventon.org/repos/berlios/diff/trunk/sventon/src/main/java/org/sventon/CheckPathExample.java?revision=HEAD&entries=/trunk/sventon/src/main/java/org/sventon/CheckPathExample.java@1325&entries=/trunk/dev/java/src/de/berlios/sventon/CheckPathExample.java@194
So it looks like the "entries" label allows different versions to be diff'd.
I'm not sure if the diffprev.svn command exists anymore, and it may have been replaced by diff. I couldn't get it or showfile.svn to work from the web-browser address line. Looks like they've replaced "showfile.svn?path=" with simply "show", and "diffprev.svn?path=" with "diff". But I am new to this and only just starting to play with the linking between Jira and web clients.
Ros
Apr 17, 2009
Ros Archer says:
I've got Sventon 2.0.5 integrated with Jira, so I thought I'd share the updated ...I've got Sventon 2.0.5 integrated with Jira, so I thought I'd share the updated URLs.
#--------------------------------- Sventon http://www.sventon.org #--------------------------------- #linkformat.changeset=http://your.host.address/svn/"repo-name"/info?revision=${rev} #linkformat.file.added=http://your.host.address/svn/"repo-name"/goto${path}?revision=${rev} #linkformat.file.modified=http://your.host.address/svn/"repo-name"/diff/?entries=${path}@${rev-1}&entries=${path}@${rev}&style=sidebyside #linkformat.file.replaced=http://your.host.address/svn/"repo-name"/goto${path}?revision=${rev} #linkformat.file.deleted=http://your.host.address/svn/"repo-name"/goto${path}?revision=${rev-1} #linkformat.copyfrom=http://your.host.address/svn/"repo-name"/goto${path}?revision=${rev-1} #The URL specification is given at http://wiki.sventon.org/index.php?n=Main.URLSpecification. The URLs will work for both Files and Directories.
Hope that helps someone. Up until yesterday we were going to go down the path of Polarion's SVN Web Client, which comes pre-configured in the Jira plugin, but it doesn't handle multiple repositories properly so when flicking between projects that point to different repositories it still thinks it's looking in the first repository. Many users have reported the bug so hopefully it gets sorted soon.
However, after playing with Sventon, I'm thinking that Sventon is better suited for our needs. It displays a list of available repositories, can handle multiple repositories and it doesn't allow Deletes, Adds, Modifications or Commits from the browser. We want to be able to enforce that developers do the developing in TortoiseSVN where we've set up the Properties to link properly with Jira.
Apr 10, 2007
Robert Brown says:
Great plugin, I think version control tie in is essential for a real ticketing s...Great plugin, I think version control tie in is essential for a real ticketing solution.
One question I have though is why was a pull/polling approach used versus having an SVN hook that pushes a checkin comment into Jira? It seems the pull/polling provides less traceability since tickets can be moved and will no longer correlate with the original checkin message. Also, if a ticket is closed before the polling, the message doesn't seem to get picked up.
Apr 16, 2007
Sean Dockery says:
While auditing our Subversion logs for a recent product release, we've discovere...While auditing our Subversion logs for a recent product release, we've discovered some issues where some Subversion commits were associated to the wrong JIRA issue. I've enabled the ability to edit Subversion log messages and fixed the incorrect commit messages.
I've waited for a while for things to correct themselves, but they haven't yet. So, I'm getting a little impatient and wondering if I actually have to intervene to fix things.
Do I have to do anything special to get the commit messages to appear under the correct JIRA issue? I've attempted to re-index JIRA (with no apparent immediate effect), and I have reduced the Subversion Reindex Service plug-in delay to restart the service immediately. I've noticed that there are files in .../data/indexes/plugins/atlassian-subversion-revisions, but I don't want to delete anything without some guidance.
Thanks for your time.
Apr 25, 2007
Sean Dockery says:
I got my answer from Atlassian support: Can you delete the <JIRA index direc...I got my answer from Atlassian support:
Can you delete the <JIRA index directory>\plugins directory and then do a reindex on JIRA?
I tried this (after backing up the indexes/plugins directory), and after the Subversion Re-Indexing Service ran to rebuild the Subversion comments, all Subversion comments in JIRA were restored along with the appropriate comments from the modified Subversion commit log messages.
May 25, 2007
Tobias Anstett says:
Hi, is this plugin compatible with svn 1.4.2 ?Hi, is this plugin compatible with svn 1.4.2 ?
May 25, 2007
Tobias Anstett says:
Hi, is this plugin compatible with svn 1.4.2 ?Hi, is this plugin compatible with svn 1.4.2 ?
Jun 12, 2007
Brian Hegeman says:
I'm interested in using the connection between JIRA issues and SVN commits provi...I'm interested in using the connection between JIRA issues and SVN commits provided by this plugin to aid our release process. From reading the other comments here, I gather that there is no direct SOAP access to the data provided by the plugin but I'm curious if there are any other methods that might help. Basically, I'd like to be able to determine all files related to a certain issue (possibly multiple commits) and check them out to a specified location. Obviously the file moving is outside the scope of the plugin but is there someway to get a list of affected files for some JIRA issue?
thanks!
Jul 03, 2007
Libor Kramolis says:
Hello. Which SVN command represents property linkformat.file.replaced? I do not...Hello.
Which SVN command represents property linkformat.file.replaced? I do not know how to set up link to ViewVC. What "file replaced" means?
Thanks,
Libor
Aug 21, 2007
Uwe Voellger says:
Hello, I would like to use JIRA together with Subversion in an one-JIRA - multi...Hello,
I would like to use JIRA together with Subversion in an one-JIRA - multi-project - multi-subversion - environment. In this environment, I expect problems with the changes reported by the JIRA-Subversion plugin.
For the plugin, it is possible to configure several Subversion repositories. One could configure all repositories that are linked together via the "externals" attribute in Subversion to make sure all check ins are found.
But the repositories tied together for a project may differ between versions of the same product (and of course between different products). Unlike the externals attribute in Subversion, the configuration in the plugin does not depend on the product or product version. Therefore the list of repositories scanned by JIRA may be inaccurate for a specific product version. In case a developer uses a wrong check in comment (referencing an project that no longer uses this code), the changes are added to an JIRA issue of a product that does not use this source at all.
Therefore I try to find out how to configure only one entry point for JIRA into Subversion, and let JIRA scanning the Subversion logs recursively including following all externals attributes. Is this possible?
Thanks,
Uwe
Sep 09, 2007
Peter Wu says:
When using multiple SVN, I encounter the following error when starting JIRA, and...When using multiple SVN, I encounter the following error when starting JIRA, and JIRA won't start:
Version 0.9.11
2007-09-10 12:05:31,875 main ERROR [plugin.ext.subversion.MultipleSubversionRepo
sitoryManagerImpl] Could not load properties from subversion-jira-plugin.propert
ies
com.atlassian.jira.InfrastructureException: Could not load properties from subve
rsion-jira-plugin.properties
My properties file:
svn.root.1=http://192.168.1.111/svn/
svn.root.2=http://192.168.1.222/repos/xxx
svn.display.name.1=XXX Development SVN
svn.display.name.2=XXX Website Model SVN
Sep 10, 2007
Christopher Fitch says:
I am having an issue with the Jira-SVN plugin and integration with ViewVC Versi...I am having an issue with the Jira-SVN plugin and integration with ViewVC
Version info: Jira ver 3.10, Jira-SVN plugin ver 0.9.11, ViewVC ver 1.0.4
Background:
We have a number of SVN repositories setup with the following URLs.
https://our.svn.server/svn/RepositoryA
https://our.svn.server/svn/RepositoryB
https://our.svn.server/svn/RepositoryC
etc...
We have our commits picked up just fine and the plugin generates the ViewVC links to the changed files.
This is where the issue occurs. The ViewVC configuration section has the following properties:
linkformat.changeset=http://svn.server/cgi-bin/viewvc.cgi$(path)/?revision=$(rev)&pathrev=$(rev)
linkformat.file.added=http://svn.server/cgi-bin/viewvc.cgi$(path)?root=svn&pathrev=$(rev)
linkformat.file.modified=http://svn.server/cgi-bin/viewvc.cgi$(path)?root=svn&pathrev=$(rev)&view=diff&r1=$(rev)&r2=$(rev-1)&diff_format=h
....
The links generated are invalid since this config forces a root=svn parameter/value pair like this:
http://svn.server/cgi-bin/viewvc.cgi$(path)?root=svn&pathrev=$(rev)
However, ViewVC needs repository roots for each separate rep like this for example:
http://svn.server/cgi-bin/viewvc.cgi$(path)?root=RepositoryA&pathrev=$(rev)
http://svn.server/cgi-bin/viewvc.cgi$(path)?root=RepositoryB&pathrev=$(rev)
etc ...
Any ideas on how I can change the config to pick this up or is there some option that I can change or is this not currently possible?
Thanks
Jan 14, 2008
Tal Abramson says:
I have the exact same question i am using ViewVC root_parents , and would...I have the exact same question
i am using ViewVC root_parents , and would like to know how to configure the plugin to work with all repo's
have we missed something in the docs?
Jan 23, 2008
Ian Daniel [Atlassian] says:
Hi Christopher and Tal, You describe the link formats for additional repositori...Hi Christopher and Tal,
You describe the link formats for additional repositories using this syntax:
Having previously specified the URL for the additional repositories using this syntax:
This is described in the subversion-jira-plugin.properties file.
Kind regards,
Ian
Jan 23, 2008
Tal Abramson says:
Thanks for the reply i figured that one out by myself at the end , but now i to...Thanks for the reply
i figured that one out by myself at the end , but now i took a closer look
and i found the instructions in the properties files at the button
maybe you should move it up , place it in the WEB LINKING instructions area
(the lines -
#linkformat.changeset.1=...
#linkformat.file.added.1=... )
best regards
Tal
Sep 24, 2007
Peter Brandström says:
We are attempting a move from CVS to Subversion, and have some difficulties with...We are attempting a move from CVS to Subversion, and have some difficulties with the Subversion plugin's log parsing.
In Jira we have a project called HLW. In CVS we have a project called HLW with tags. When we migrate from CVS to Subversion we use cvs2svn which creates the following log message:
This commit was manufactured by cvs2svn to create tag 'f-HLW-1-0-0-0'.
Since there is a Jira HLW project, this causes the Subversion plugin to pick up the HLW-1 part of the tag above, and link the log message to the issue HLW-1. This generates the following message in the HLW-1 issue, about 15 times (there are 15 tags):
Files Changed ADD /comp/hlw/tags/f-HLW-1-0-0-0 (from /comp/hlw/trunk)
Which isn't very interesting since the issue isn't related to the message. We probably have around 100 projects to move.
Any ideas on how stop the plugin from picking up these log messages? I had a look at the code and it seems you use a generic link parsing function supplied by Jira, which doesn't allow you to change the regexp used for issue matching in strings. Which is funny, because you can change the valid project key regexp.
Cheers,
Peter
PS Thanks for a great product and plugin
Nov 16, 2007
Thomas Mortimer says:
What is the accepted/normal/correct way to have the subversion plugin re-scan, s...What is the accepted/normal/correct way to have the subversion plugin re-scan, say once a night, for edited SVN log messages?
Thanks,
-Tom
Nov 18, 2007
Ian Daniel [Atlassian] says:
Hi Thomas, Unfortunately the only way to do what you want is to: stop JIRA d...Hi Thomas,
Unfortunately the only way to do what you want is to:
There is an existing improvement request for this shortcoming: http://jira.atlassian.com/browse/SVN-59. Feel free to vote for that issue or comment on why it is important to you.
Kind regards,
Ian
Dec 07, 2007
Stephen Waga says:
Great work on the plugin. Is it possible to configure the plugin so that it only...Great work on the plugin.
Is it possible to configure the plugin so that it only tracks changes for a specific Jira project?
Additionally, is it possible to have the subversion tab appear only for targeted Jira projects?
Thanks in advance.
I am using the 0.9.8 version of the plugin for Jira version 3.7.3 - #187.
Steve
Dec 09, 2007
Ian Daniel [Atlassian] says:
Hi Stephen, Unfortunately it isn't possible to do this. There is an existing fe...Hi Stephen,
Unfortunately it isn't possible to do this. There is an existing feature request: http://jira.atlassian.com/browse/SVN-42. Please feel free to vote for that issue or add a comment indicating why it would be important for you.
Kind regards,
Ian
Dec 19, 2007
Vishwajeet Singh says:
Hi Daniel, I think you can help me on this. I commited at file level not at di...Hi Daniel,
I think you can help me on this.
I commited at file level not at directory level but by selecting single file in my working copy which is checked out from Subversion. I entered issue ID and commited my changes but I can not see my commit in JIRA Subversion commits tab.
If same commit I do at direcory level I am able to see my commit. Is this bug in Subversion plugin or something needs to be done for same. Interestingly if I see subversion log I can see Issue Id and Click on it to reach at issue.
Thanks for your help
Regards
Vishwajeet Singh
Dec 19, 2007
Ian Daniel [Atlassian] says:
Hi Vishwajeet, I see you have also raised this in http://jira.atlassian.com/bro...Hi Vishwajeet,
I see you have also raised this in http://jira.atlassian.com/browse/SVN-168. I will respond there.
Kind regards,
Ian
Jan 29, 2008
Thoralf Will says:
Edit project function broken? Somehow I cannot edit a repository once it's adde...Edit project function broken?
Somehow I cannot edit a repository once it's added. I wanted to adjust the urls for the project because the viewvc doesn't match our server setup but it simply ignores the changes. I have to delete the project and add it anew which is quite a waste of time.
Additionally the page hangs when I add a project. This is reproducable. Every time when I add a project it will load until eternity - but the project is added properly.
Jul 14, 2008
Ian Daniel [Atlassian] says:
Hi Thoralf, Somehow I cannot edit a repository once it's added. I wanted to ad...Hi Thoralf,
I think you may be running into SVN-180. Until we release a new version of the plugin, please don't use the properties file - remove it from WEB-INF/classes and restart - and instead make your changes from within JIRA.
I cannot reproduce this behaviour on my test instance. Can you please create a support case in https://support.atlassian.com and attach:
We will then investigate. Thanks.
Feb 04, 2008
Igor Muratov says:
Hello How to configure this plugin with SVN over HTTPS+SSL authentification. We...Hello
How to configure this plugin with SVN over HTTPS+SSL authentification. We use authentification by SSL certificates and I can't find any information how to configure JIRA as https client with client's certificate.
Feb 05, 2008
David Donn says:
Hi, I'm getting an NPE using plugin version 0.10.1 with JIRA version 3.12.1. It...Hi,
I'm getting an NPE using plugin version 0.10.1 with JIRA version 3.12.1. It occurs when in the Subversion tab of an issue.
Any ideas?
Thanks in advance,
David
The error:
2008-02-06 09:04:23,183 http-8180-Processor24 ERROR [subversion.issuetabpanels.changes.SubversionRevisionsTabPanel] Error retrieving actions for : PI-7060 java.lang.NullPointerException at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.getLogEntriesByRepository(RevisionIndexer.java:489) at com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.SubversionRevisionsTabPanel.getActions(SubversionRevisionsTabPanel.java:36) at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelModuleDescriptor.getActions(IssueTabPanelModuleDescriptor.java:99) at com.atlassian.jira.web.action.issue.ViewIssue.getActions(ViewIssue.java:400) 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:597) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:61) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:52) at webwork.util.ValueStack.findValue(ValueStack.java:346) at webwork.util.ValueStack.findValue(ValueStack.java:175) at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.java:61) at webwork.view.taglib.BasicPropertyTag.doStartTag(BasicPropertyTag.java:54) at org.apache.jsp.includes.panels.issue.actions_jsp._jspService(actions_jsp.java:254) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) at org.apache.jsp.secure.views.issue.viewissue_jsp._jspService(viewissue_jsp.java:321) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:281) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) .. etc .. etcMy config file:
#---------------------------------------- # SUBVERSION PROPERTIES #---------------------------------------- # NOTE: New from version 0.6 is support for multiple svn repositories. You can specify a default repository # with the same syntax as before (svn.root = {svn root}, etc...). You can now specify additional repositories # with: svn.root.1=..., svn.root.2=..., and so on. If you do not specify the username, password, view url, # revision indexing, and revision indexing cache size for you additional repository entries then the values # will be taken from your default repository entry (in this way you do not need to copy username and password # over and over if they are the same). You should note that there is also a new property, svn.dislay.name # which, when specified, will be shown on the log page and will identify the repository. If this property # is not specifed then the svn root will be used. # Full path to the Subversion root - at the moment svn://, svn+ssh://, http:// and https:// are supported. svn.root=http://svn.internal.pacific.net.au/repository/development #svn.root=svn://localhost/repos #svn.root=http://svn.apache.org/repos/asf/forrest/trunk #svn.root=svn://svn.cargo.codehaus.org/cargo/scm/cargo/trunk # Note that this plugin now supports multiple repositories with the follwing syntax #svn.root.1=//localhost/otherRepos # Subversion repository display name - can include HTML, eg. <a href="http://svn.mycompany.com/">SVN Repo</a> svn.display.name=PIAU Systems SVN #svn.display.name.1=My Other Repository # Subversion username svn.username=jira_owner #svn.username=mike #svn.username.1=mark # Subversion password svn.password=r3zrTZ40 #svn.password=chocolate #svn.password.1=icecream # OpenSSH private key file #Please note: The passphrase for the private key file is contained in "svn.password". #svn.privatekeyfile=C:/PuTTY/privatekey.openssh #svn.privatekeyfile.1=/home/subversion/privatekey.openssh #---------------------------------------- # WEB LINKING #---------------------------------------- # If you specify the URL of your ViewCVS/ViewSVN/Fisheye server, JIRA will hyperlink file entries, # change lists and jobs to it. Format is configurable, with the following variables replaced at # runtime: # ${path} - Path to the changed file or directory # ${rev} - Subversion revision of the change # ${rev-1} - Subversion revision of the change, minus 1 #--------------------------------- # ViewCVS (1.0-DEV) #--------------------------------- #linkformat.changeset=http://your.host.address/viewcvs?view=rev&rev=${rev} #linkformat.file.added=http://your.host.address/viewcvs.cgi/${path}/?rev=${rev}&view=markup #linkformat.file.modified=http://your.host.address/viewcvs.cgi/${path}/?rev=${rev}&view=diff&r1=${rev}&r2=${rev-1}&p1=${path}&p2=${path} #linkformat.file.replaced=http://your.host.address/viewcvs.cgi/${path}/?rev=${rev}&view=markup #linkformat.file.deleted=http://your.host.address/viewcvs.cgi/${path}/?rev=${rev-1}&view=markup #linkformat.copyfrom=http://your.host.address/viewcvs.cgi/${path}?rev=${rev-1}&view=markup # linkformat.changeset.1=... # linkformat.file.added.1=... #--------------------------------- # ViewVC 1.0.1 #--------------------------------- #linkformat.changeset=http://your.host.address/viewvc?root=svn&revision=${rev}&view=rev #linkformat.file.added=http://your.host.address/viewvc${path}/?revision=${rev}&view=markup&pathrev=${rev}&root=svn #linkformat.file.modified=http://your.host.address/viewvc${path}/?revision=${rev}&r1=${rev}&r2=${rev-1}&root=svn #linkformat.file.replaced=http://your.host.address/viewvc${path}/?revision=${rev}&view=markup&root=svn #linkformat.file.deleted=http://your.host.address/viewvc${path}?pathrev=${rev-1}&view=markup&root=svn #linkformat.copyfrom=http://your.host.address/viewvc${path}?revision=${rev-1}&view=markup&root=svn #--------------------------------- # ViewVC 1.0.3 #--------------------------------- #linkformat.changeset=http://192.168.0.100/viewvc?root=svn&revision=${rev}&view=rev #linkformat.file.added=http://192.168.0.100/viewvc${path}/?revision=${rev}&view=markup&pathrev=${rev}&root=svn #linkformat.file.modified=http://192.168.0.100/viewvc${path}/?revision=${rev}&r1=${rev}&r2=${rev-1}&root=svn #linkformat.file.replaced=http://192.168.0.100/viewvc${path}/?revision=${rev}&view=markup&root=svn #linkformat.file.deleted=http://192.168.0.100/viewvc${path}?pathrev=${rev-1}&view=markup&root=svn #linkformat.copyfrom=http://192.168.0.100/viewvc${path}?revision=${rev-1}&view=markup&root=svn #--------------------------------- # ViewVC 1.0.4 #--------------------------------- #linkformat.changeset=http://your.host.address/viewvc?root=svn&revision=${rev}&pathrev=${rev}&view=rev #linkformat.file.added=http://your.host.address/viewvc${path}?root=svn&pathrev=${rev} #linkformat.file.modified=http://your.host.address/viewvc${path}?root=svn&pathrev=${rev}&view=diff&r1=${rev}&r2=${rev-1}&diff_format=h #linkformat.file.deleted=http://your.host.address/viewvc${path}?root=svn&pathrev=${rev-1} #linkformat.copyfrom=http://your.host.address/viewvc${path}?root=svn&pathrev=${rev-1}&view=markup #--------------------------------- # FishEye #--------------------------------- linkformat.changeset=http://svn.atlassian.com/fisheye/changelog/public?cs=${rev} linkformat.file.added=http://svn.atlassian.com/fisheye/viewrep/public${path}?r=${rev} linkformat.file.modified=http://svn.atlassian.com/fisheye/viewrep/public${path}#${rev} linkformat.file.replaced=http://svn.atlassian.com/fisheye/viewrep/public${path}#${rev} linkformat.file.deleted=http://svn.atlassian.com/fisheye/viewrep/public${path} linkformat.copyfrom=http://svn.atlassian.com/fisheye/viewrep/public${path} # #linkformat.changeset.1=... #linkformat.file.added.1=... #--------------------------------- # WebClient for SVN #--------------------------------- #linkformat.changeset=http://your.host.address/svnwebclient/revisionDetails.jsp?location=/&rev=${rev} #linkformat.file.added=http://your.host.address/svnwebclient/changedResource.jsp?location=/&url=${path}&rev=${rev}&action=add #linkformat.file.modified=http://your.host.address/svnwebclient/changedResource.jsp?location=/&url=${path}&rev=${rev}&action=modify #linkformat.file.replaced=http://your.host.address/svnwebclient/changedResource.jsp?location=/&url=${path}&rev=${rev}&action=replace #linkformat.file.deleted=http://your.host.address/svnwebclient/changedResource.jsp?location=/&url=${path}&rev=${rev}&action=delete #linkformat.copyfrom=http://your.host.address/svnwebclient/changedResource.jsp?location=/&url=${path}&rev=${rev}&action=add #---------------------------------------- # REVISION INDEXING #---------------------------------------- # # if this property is uncommented and set to true, every revision in Subversion will be indexed # and linked to any mentioned issue keys revision.indexing=true #revision.indexing.1=true # the number of revisions to keep cached in memory for quick retrieval # note: this number does not affect the speed with which revisions are looked up from the index (to get revisions for a given issue) # this affects the speed at which the full content of those revisions are retrieved from SVN. revision.cache.size=10000 #revision.cache.size.1=20000Feb 05, 2008
Ian Daniel [Atlassian] says:
Hi David, If you have a current maintenance licence for JIRA, can you please cr...Hi David,
If you have a current maintenance licence for JIRA, can you please create a support case in https://support.atlassian.com and we will investigate this. Can you please attach to the support case:
Can you also please copy and paste the entire contents of the Administration > System Info page into your reply, so that we know the details of your JIRA configuration.
Finally, can you let us know (in the support case) whether this error occurs for all issues that have a subversion commits associated with them, or only with issue PI-7060.
Kind regards,
Ian
Feb 05, 2008
David Donn says:
Thanks Ian, the problem seems only to affect some issues. I have created a supp...Thanks Ian,
the problem seems only to affect some issues. I have created a support case here
Regards,
David
Feb 12, 2008
Erin says:
Hi! I'm using 0.10.1 with Jira Enterprise 3.12.1, WAR version. I installed t...Hi! I'm using 0.10.1 with Jira Enterprise 3.12.1, WAR version. I installed this plugin exactly as README.txt said to, and I can't get Jira to start now. Here are the latest entries in atlassian-jira.log:
2008-02-12 00:00:00,033 JiraQuartzScheduler_Worker-0 INFO [issue.index.job.OptimizeIndexJob] Optimize Index Job running...
2008-02-12 00:00:00,078 JiraQuartzScheduler_Worker-0 INFO [issue.index.job.OptimizeIndexJob] Indexes Optimized. Took: 21 milliseconds.
2008-02-12 00:00:00,079 JiraQuartzScheduler_Worker-0 INFO [issue.index.job.OptimizeIndexJob] Optimize Index Job complete.
2008-02-12 04:10:03,231 JiraQuartzScheduler_Worker-0 INFO [jira.action.admin.DataExport] Export took 690ms
2008-02-12 04:10:03,234 JiraQuartzScheduler_Worker-0 INFO [jira.action.admin.DataExport] Wrote 1902 entities to export
2008-02-12 09:55:22,218 http-8443-Processor12 INFO [jira.action.admin.DataExport] Export took 4028ms
2008-02-12 09:55:22,220 http-8443-Processor12 INFO [jira.action.admin.DataExport] Wrote 1902 entities to export
2008-02-12 16:11:02,963 JiraQuartzScheduler_Worker-0 INFO [jira.action.admin.DataExport] Export took 475ms
2008-02-12 16:11:02,967 JiraQuartzScheduler_Worker-0 INFO [jira.action.admin.DataExport] Wrote 1938 entities to export
2008-02-12 16:45:44,922 ContainerBackgroundProcessor[StandardEngine[Catalina]] WARN [ContainerBase.[Catalina].[localhost].[/jira]] Cannot serialize session attribute seraph_defaultauthenticator_user for session 8621BE59FB81C9FFB54B55C4B6C41145
java.io.NotSerializableException: org.apache.log4j.Logger
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
etc
2008-02-12 16:45:44,939 ContainerBackgroundProcessor[StandardEngine[Catalina]] WARN [ContainerBase.[Catalina].[localhost].[/jira]] Cannot serialize session attribute jira.user.dashboard.portal.configs for session 3A284B32F53139C86E2239BE74C6D557
java.io.NotSerializableException: com.atlassian.jira.portal.PortalPageConfigurationImpl
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
etc
2008-02-12 16:45:44,947 ContainerBackgroundProcessor[StandardEngine[Catalina]] WARN [ContainerBase.[Catalina].[localhost].[/jira]] Cannot serialize session attribute seraph_defaultauthenticator_user for session 3A284B32F53139C86E2239BE74C6D557
java.io.NotSerializableException: org.apache.log4j.Logger
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
etc
2008-02-12 16:48:18,492 ContainerBackgroundProcessor[StandardEngine[Catalina]] INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 3.12.1-#299
2008-02-12 16:48:18,494 ContainerBackgroundProcessor[StandardEngine[Catalina]] INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: postgres72
2008-02-12 16:48:18,623 ContainerBackgroundProcessor[StandardEngine[Catalina]] INFO [atlassian.jira.upgrade.ConsistencyCheckImpl]
******************************************************************************************************
JIRA 3.12.1 build: 299 (Enterprise Edition) started. You can now access JIRA through your web browser.
******************************************************************************************************
2008-02-12 16:48:18,631 ContainerBackgroundProcessor[StandardEngine[Catalina]] ERROR [util.system.check.JRA10145Check] WARNING: Apache Tomcat/5.5.25 server and the 'org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER' system property is not set to true!This can result in OutOfMemoryErrors. For more information please see: http://www.atlassian.com/software/jira/docs/latest/servers/tomcat55.html
2008-02-12 16:48:19,603 ContainerBackgroundProcessor[StandardEngine[Catalina]] WARN [webwork.dispatcher.ServletDispatcher] Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
2008-02-12 16:48:20,350 JiraQuartzScheduler_Worker-0 ERROR [jira.action.admin.DataExport] Error exporting: java.lang.NullPointerException
java.lang.NullPointerException
at org.ofbiz.core.util.Debug.isOn(Debug.java:163)
etc
2008-02-12 16:48:20,362 JiraQuartzScheduler_Worker-0 ERROR [atlassian.jira.service.ServiceRunner] Error occured while executing the service [ Container: com.atlassian.jira.service.services.export.ExportService delay [43200000ms]]
java.lang.NoClassDefFoundError: com/atlassian/jira/web/filters/ThreadLocalQueryProfiler$DataPointStore
at com.atlassian.jira.web.filters.ThreadLocalQueryProfiler.<init>(ThreadLocalQueryProfiler.java:70)
etc
2008-02-12 16:48:20,366 JiraQuartzScheduler_Worker-0 ERROR [org.quartz.simpl.SimpleThreadPool] Error while executing the Runnable:
org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:538)
etc
Caused by: java.lang.NullPointerException
at org.apache.log4j.LogManager.getLogger(LogManager.java:179)
etc
2008-02-12 16:48:58,328 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 3.12.1-#299
2008-02-12 16:48:58,330 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: postgres72
2008-02-12 16:48:58,507 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl]
******************************************************************************************************
JIRA 3.12.1 build: 299 (Enterprise Edition) started. You can now access JIRA through your web browser.
******************************************************************************************************
2008-02-12 16:48:58,518 main ERROR [util.system.check.JRA10145Check] WARNING: Apache Tomcat/5.5.25 server and the 'org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER' system property is not set to true!This can result in OutOfMemoryErrors. For more information please see: http://www.atlassian.com/software/jira/docs/latest/servers/tomcat55.html
2008-02-12 16:48:58,628 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] File /srv/jira-backups/2008-Feb-12--1648.zip exists already.
2008-02-12 16:48:59,837 main WARN [webwork.dispatcher.ServletDispatcher] Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
Where do I start checking this error? Could it have anything to do with the fact that my svn.passwords are all blank? I have specified 15 repos. Is that too many?
Feb 12, 2008
Ian Daniel [Atlassian] says:
Hi Erin, If you have a current maintenance licence for JIRA, or if you are eval...Hi Erin,
If you have a current maintenance licence for JIRA, or if you are evaluating JIRA, can you please create a support case in https://support.atlassian.com and we will investigate this. Can you please attach to the support case:
Can you also copy and paste the entire contents of the Administration > System Info page into your support request, so that we know the details of your JIRA configuration.
Can you please just try one repository, rather than 15, and see if that works. Let us know the result in your support case.
Kind regards,
Ian
Feb 13, 2008
Erin says:
Thanks, issue number is JSP-19988.Thanks, issue number is JSP-19988.
Feb 12, 2008
Ed Callahan says:
Question regarding the service index interval. It defaults to one hour, per abov...Question regarding the service index interval. It defaults to one hour, per above. OK. However, the team here previously used a setup where SVN pushed in the defect tracking system. So the hour delay is not working for them. Thus....
Is there a minimal time value ? What are the expected resource trade offs for lower values ? It likely 'depends', so what are the key dependency factors ?
Thanks.
Feb 24, 2008
Ian Daniel [Atlassian] says:
Hi Ed, The minimum time value is one minute. The Subversion plugin index servi...Hi Ed,
The minimum time value is one minute.
The Subversion plugin index service retrieves the log messages since the last revision that it retrieved, and indexes any message that has a JIRA issue key in it.
The key dependency factors are the size of your repository and the number of changes since the last revision that the service retrieved.
Kind regards,
Ian
Feb 20, 2008
Bogdan Calmac says:
Is the administration interface available with JIRA 3.11 professional and plugin...Is the administration interface available with JIRA 3.11 professional and plugin 0.9.12? The plugin works properly, but I don't see "Subversion Repository" under "Administration > Global Settings". I am logged in as admin.
Thanks.
Feb 24, 2008
Ian Daniel [Atlassian] says:
Hi Bogdan, The administration interface was added to version 0.10.0 of the plug...Hi Bogdan,
The administration interface was added to version 0.10.0 of the plugin, which is for JIRA 3.12 or later.
Kind regards,
Ian
Feb 21, 2008
Erin says:
Are there any authentication issues regarding using https + certificate authenti...Are there any authentication issues regarding using https + certificate authentication? I'm having trouble authenticating through this plugin -- repository listed as inactive due to handshake failure -- but I can authenticate on commandline from my server. I'm using the latest version of the plugin with Jira 3.12.1 Enterprise.
Feb 24, 2008
Ian Daniel [Atlassian] says:
Hi Erin, I believe we are handling this in your support case JSP-19988. Kind r...Hi Erin,
I believe we are handling this in your support case JSP-19988.
Kind regards,
Ian
Feb 26, 2008
Klueze says:
Hello. I am running Jira Standalone 3.12.1with your plugin. It works fine, but ...Hello.
I am running Jira Standalone 3.12.1with your plugin. It works fine, but if i add more then 2 commits i got this error:
2008-02-26 10:10:29,076 http-8080-Processor25 ERROR [subversion.issuetabpanels.c
hanges.SubversionRevisionsTabPanel] Error retrieving actions for : TESTPROJECT-1
java.lang.NullPointerException
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.ge
tLogEntriesByRepository(RevisionIndexer.java:489)
at com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.Subve
rsionRevisionsTabPanel.getActions(SubversionRevisionsTabPanel.java:36)
at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelModuleDescriptor
.getActions(IssueTabPanelModuleDescriptor.java:99)
at com.atlassian.jira.web.action.issue.ViewIssue.getActions(ViewIssue.ja
va:400)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtil
s.java:61)
at webwork.util.InjectionUtils.invoke(InjectionUtils.java:52)
at webwork.util.ValueStack.findValue(ValueStack.java:346)
at webwork.util.ValueStack.findValue(ValueStack.java:175)
at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSup
port.java:61)
at webwork.view.taglib.BasicPropertyTag.doStartTag(BasicPropertyTag.java
:54)
at org.apache.jsp.includes.panels.issue.actions_jsp._jspService(actions_
jsp.java:254)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:334)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3
14)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD
ispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis
patcher.java:499)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary
.java:966)
at org.apache.jsp.secure.views.issue.viewissue_jsp._jspService(viewissue
_jsp.java:321)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:334)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3
14)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica
tionDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD
ispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis
patcher.java:301)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraS
ervletDispatcher.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica
tionDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD
ispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis
patcher.java:301)
at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.
java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilt
er.java:73)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilt
er.java:119)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilte
r.java:55)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.ja
va:192)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(Truste
dApplicationsFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.
java:110)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(Profili
ngFilter.java:132)
at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfi
lingFilter.java:16)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(Acti
onCleanupDelayFilter.java:43)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestC
leanupFilter.java:50)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(Abstract
JohnsonFilter.java:72)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewrit
eFilter.java:350)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEn
codingFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFil
ter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:
541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Thread.java:619)
what can i do?
Feb 28, 2008
Tal Abramson says:
i an getting the same exception But for me it's a different scenario When i add ...i an getting the same exception
But for me it's a different scenario
When i add a new repository , old commits are not shown , and getting this exception
help
Mar 11, 2008
Adrian Moisey says:
Everytime I add a link for ViewVW, it just doesn't work. I click save and ...Everytime I add a link for ViewVW, it just doesn't work. I click save and its as if nothing got added. Any ideas how I can get this working?
Mar 11, 2008
Ian Daniel [Atlassian] says:
Hi, If you have a current maintenance licence for JIRA, or if you are evaluatin...Hi,
If you have a current maintenance licence for JIRA, or if you are evaluating JIRA, can you please create a support case in https://support.atlassian.com, with the details of the problem, and we will investigate it. Can you please attach to the support case:
Can you also copy and paste the entire contents of the Administration > System Info page into your support request, so that we know the details of your JIRA configuration.
You say you "click save and its as if nothing got added". Where are you clicking save? IS this in a screen in JIRA, or in a file, or...? Can you please provide details in your support case.
Kind regards,
Ian
Mar 11, 2008
Ian Daniel [Atlassian] says:
Hi Adrian, My apologies, I see that you have already created a support case. We...Hi Adrian,
My apologies, I see that you have already created a support case. We will address the issue there.
Kind regards,
Ian
Mar 11, 2008
Ian Daniel [Atlassian] says:
I've reported this to Adrian on his support case, but for anyone else with a sim...I've reported this to Adrian on his support case, but for anyone else with a similar problem, it is a bug in the Subversion plugin: http://jira.atlassian.com/browse/SVN-190.
Mar 19, 2008
Adrian Smith says:
The bug SVN-190 has been marked as resolved but there's no detail about what was...The bug SVN-190 has been marked as resolved but there's no detail about what was done to fix it. I'm having the same problem as Adrian Moiser, i.e when I change any of the web link settings for a repository they don't appear on the main Subversion Repositories settings page. The strange this is that they are in the database in the propertyentry and propertystring tables. Any idea what's causing this problem?
Mar 24, 2008
Ian Daniel [Atlassian] says:
There will be a new release of the plugin out soon, hopefully this week. It will...There will be a new release of the plugin out soon, hopefully this week. It will contain the fix for SVN-190.
Mar 27, 2008
Vishwajeet Singh says:
Hi Ian, If I change Issue Id which was linked to Jira already to some other Iss...Hi Ian,
If I change Issue Id which was linked to Jira already to some other Issue Id by editing Subversion log. will jira reindex and change to other Issue.
For eg Suppose I linked a commit to TST-1 and Jira Indexes it and links but later I changed TST-1 to TST-2 by editing log message will Jira link this commit to TST-2 or not. As of now I am not able to see the changes which I am expecting
Please help.
Thanks,
Vishwajeet
Mar 30, 2008
Ian Daniel [Atlassian] says:
Hi Vishwajeet, The Subversion plugin will not pick up changes to existing logs....Hi Vishwajeet,
The Subversion plugin will not pick up changes to existing logs. This is a known limitation: http://jira.atlassian.com/browse/SVN-59.
The only way to pick up the changes is to delete the plugins/atlassian-subversion-revisions folder under your indexes folder, then restart JIRA. This will result in the whole Subversion repository being reindexed.
Kind regards,
Ian
Mar 28, 2008
Tobias Keller says:
Hi, I've installed Version 0.10.2 on a JIRA 3.12.2 system. I'm able to connect ...Hi,
I've installed Version 0.10.2 on a JIRA 3.12.2 system. I'm able to connect to the example repository via http. If I try to connetc to one of our SVN repositorys via svn+ssh I'm getting the following error message:
HTTP Status 404 - Could not execute action [AddSubversionRepository]:com/trilead/ssh2/InteractiveCallback<p><small><small><pre>java.lang.NoClassDefFoundError: com/trilead/ssh2/InteractiveCallback at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:70) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:60) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:974) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.testConnection(SVNRepositoryImpl.java:69) at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.activate(SubversionManagerImpl.java:260) at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.setup(SubversionManagerImpl.java:89) at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.<init>(SubversionManagerImpl.java:56) at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.createRepository(MultipleSubversionRepositoryManagerImpl.java:207) at com.atlassian.jira.plugin.ext.subversion.action.AddSubversionRepositoryAction.doExecute(AddSubversionRepositoryAction.java:190) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:211) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:192) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:110) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)
Any ideas whats going wrong?
Thanks in advance
Tobias
Mar 30, 2008
Ian Daniel [Atlassian] says:
Hi Tobias, If you have a current maintenance licence for JIRA, or if you are ev...Hi Tobias,
If you have a current maintenance licence for JIRA, or if you are evaluating JIRA, can you please create an issue in our support system, https://support.atlassian.com, with the details of the problem, and we will investigate it. Can you please attach to the support case:
Can you also copy and paste the entire contents of the Administration > System Info page into your support request, so that we know the details of your JIRA configuration.
Kind regards,
Ian
Apr 02, 2008
Dylan Etkin says:
Hi Tobias, I believe there is a bug with the latest version of the plugin. The ...Hi Tobias,
I believe there is a bug with the latest version of the plugin. The details can be viewed here http://jira.atlassian.com/browse/SVN-199.
This should be fixed and a new version released within the next day or so.
Sorry for the trouble,
Dylan
Apr 21, 2008
Tobias Keller says:
With the latest version (0.10.3) I'm able to connect to our repositorys without ...With the latest version (0.10.3) I'm able to connect to our repositorys without errors. Everything looks accurate now.
Cheers
Tobias
Mar 31, 2008
Vishwajeet Singh says:
Hi Ian, I am planning to write a plugin in parallel to your plugin; which will ...Hi Ian,
I am planning to write a plugin in parallel to your plugin; which will just reindex the repository based on some condition or some change made some where and update this directly in database.
So can you please give me quick pointers on how to re-index and update same in database.
And apart from that which files to look in existing plugin to get an Idea on this.
Please help
Regards,
Vishwajeet
Mar 31, 2008
Ian Daniel [Atlassian] says:
Hi Vishwajeet, Atlassian does not provide support for third-party development q...Hi Vishwajeet,
Atlassian does not provide support for third-party development queries. I suggest that you ask on our JIRA development forum. Another third-party developer may be willing to help you out.
Kind regards,
Ian
Apr 01, 2008
Peter Brandström says:
While the plugin is great, the installation isn't that straight forward. I've us...While the plugin is great, the installation isn't that straight forward. I've used a few different versions of the plugin and upgraded Jira a few times along the way.
The natural thing for a new user would be to not install the property file, in contradiction with your installation instructions step 2:
Copy subversion-jira-plugin.properties into JIRA's WEB-INF/classes.
Because as you say later, if you copy this file you cannot use the GUI to add more repositories. Just finding this file in the zip file is hard, there are a lot of files, and two with nearly identical names.
If you do not copy the property file, then you run into this problem in the logs:
2008-04-01 14:48:54,939 main INFO [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] Could not find any subversion repositories configured, trying to load from System Properties.
2008-04-01 14:48:54,958 main WARN [plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl] Problem adding a subversion manager
java.lang.NullPointerException
at java.util.Properties$LineReader.readLine(Unknown Source)
at java.util.Properties.load0(Unknown Source)
at java.util.Properties.load(Unknown Source)
at com.atlassian.jira.plugin.ext.subversion.SvnPropertiesLoader.getSVNProperties(SvnPropertiesLoader.java:26)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.loadFromProperties(MultipleSubversionRepositoryManagerImpl.java:174)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.loadSvnManagers(MultipleSubversionRepositoryManagerImpl.java:108)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:63)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
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 com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:411)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:347)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
I didn't notice this, I just went to the administration and configured a repository which was then called "Active". But there was no service running which made me suspicious. At this point you have to restart Jira to get the indexing going.
I suggest you rewrite the installation instructions so they make sense for someone installing without a property file, and add a chapter for those who already have such a file. Keep the two well separated and don't mix the instructions.
Cheers,
Peter
Apr 02, 2008
mark w says:
Just installed this plugin. Everything seems great and I am getting the Subversi...Just installed this plugin. Everything seems great and I am getting the Subversion stuff in Jira. However the issue number in the Subversion notes (as displayed in Jira) has a line through it and when I move over it i get a hint saying "Only obtaining one side of conversation". Any ideas?
Many thanks
Mark W
Apr 02, 2008
Ian Daniel [Atlassian] says:
Hi Mark, JIRA displays an issue with a line through it if it is resolved. And t...Hi Mark,
JIRA displays an issue with a line through it if it is resolved. And the hint when you hover over an issue is the issue summary. So I suspect the issue key you were hovering over is for an issue that has the summary "Only obtaining one side of conversation".
Kind regards,
Ian
Apr 07, 2008
jatin jain says:
Hi all, I am using the lugin for my jira-professional-3.12.1 and subversion. I ...Hi all,
I am using the lugin for my jira-professional-3.12.1 and subversion. I hav jira coupled with MySql.
I want to know:::
>> Does JIRA store any information in its Database (mySql here in my case), for the commits made in subversion files.
>> I want to know how does the JIRA-subversion plugin knows about the path of the files. I provide a "svn+ssh" to the repository, but with help of which "plugin-files" does it take the path out of the files to be displayed on to the "subversion" tab in jira?
What I want is to make an application that takes the jira number and show the full paths of the files to the user.
Thanks a lot,
Jatin
Apr 08, 2008
Jorge Miguel Correia says:
HI, I´ve installed svn correctly and configure it, after a restart it is brokin...HI,
I´ve installed svn correctly and configure it, after a restart it is broking my jira and all I get is a tomcat error.
My log is as follows
2008-04-08 18:13:06,000 Thread-1 INFO [jira.appconsistency.db.DatabaseCompatibilityEnforcer]
******************************************************************************************************
JIRA starting... Standard Edition, Version: 3.12.2-#300
******************************************************************************************************
2008-04-08 18:13:16,703 Thread-1 ERROR [ext.subversion.revisions.RevisionIndexer] Could not load properties from subversion-jira-plugin.properties
java.lang.IllegalArgumentException: Multiple services with name 'Subversion Revision Indexing Service' exist.
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:98)
at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:63)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.install(RevisionIndexService.java:51)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:109)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:276)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:421)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:347)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
2008-04-08 18:13:16,703 Thread-1 ERROR [com.atlassian.jira.ComponentManager] Error occurred while starting component.
com.atlassian.jira.InfrastructureException: Could not load properties from subversion-jira-plugin.properties
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:114)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:276)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:421)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:347)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: java.lang.IllegalArgumentException: Multiple services with name 'Subversion Revision Indexing Service' exist.
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:98)
at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:63)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.install(RevisionIndexService.java:51)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:109)
... 19 more
2008-04-08 18:13:16,718 Thread-1 FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A RuntimeException occurred during ConsistencyLauncher servlet context initialisation - Error occurred while starting component..
com.atlassian.jira.InfrastructureException: Error occurred while starting component.
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:427)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:347)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: com.atlassian.jira.InfrastructureException: Could not load properties from subversion-jira-plugin.properties
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:114)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:276)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:421)
... 17 more
Caused by: java.lang.IllegalArgumentException: Multiple services with name 'Subversion Revision Indexing Service' exist.
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:98)
at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:63)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.install(RevisionIndexService.java:51)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:109)
... 19 more
2008-04-08 18:13:16,718 Thread-1 ERROR [ContainerBase.[Catalina].[localhost].[/]] Exception sending context initialized event to listener instance of class com.atlassian.jira.upgrade.ConsistencyLauncher
com.atlassian.jira.InfrastructureException: Error occurred while starting component.
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:427)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:347)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: com.atlassian.jira.InfrastructureException: Could not load properties from subversion-jira-plugin.properties
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:114)
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.start(MultipleSubversionRepositoryManagerImpl.java:276)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:421)
... 17 more
Caused by: java.lang.IllegalArgumentException: Multiple services with name 'Subversion Revision Indexing Service' exist.
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:98)
at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:63)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.install(RevisionIndexService.java:51)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.start(RevisionIndexer.java:109)
... 19 more
____________________________
I´ve already deleted the index of the plugin, but it didn´t do nothing. I´ve tried with and without ubversion-jira-plugin.properties file.
The only way to get jira back to life was to deleted svn plugin jars.
I´m using plugin version 0.10.3 and jira 3.12.2
Can you check this ? Thanks
Apr 08, 2008
Ian Daniel [Atlassian] says:
If you have a current maintenance licence for JIRA, or if you are evaluating JIR...If you have a current maintenance licence for JIRA, or if you are evaluating JIRA, can you please create an issue in our support system, https://support.atlassian.com, with the details of the problem, and we will investigate it.
Apr 09, 2008
Jorge Miguel Correia says:
Hi, i´m evaluating. Thanks I will do that.Hi,
i´m evaluating. Thanks I will do that.
Apr 14, 2008
dan costelloe says:
Hi, Is it possible to use this plugin trigger the creation of new issues after...Hi,
Is it possible to use this plugin trigger the creation of new issues after a commit? For example, say you have 2 streams of code, maintenance and development. In order to keep the development stream up to date with bugfixes on the maintenance stream, it would be cool to auto-create an issue in Jira every time there is a commit to the maintenance stream - making it easier to keep track of the roll-up. I've hunted around the documentation for something like this but I think I may be missing the correct search terms. Any info on how the above could be achieved would be appreciated.
Cheers.
dan
Apr 14, 2008
Ian Daniel [Atlassian] says:
Hi Dan, The Subversion plugin does not support this, however you could use a Su...Hi Dan,
The Subversion plugin does not support this, however you could use a Subversion trigger to achieve this, with the trigger producing an email that is sent to your JIRA instance and results in a new issue being created.
Kind regards,
Ian
Apr 16, 2008
dan costelloe says:
Ian, you're a legend - thanks for that it was just what I was looking for. One...Ian, you're a legend - thanks for that it was just what I was looking for.
One final question though if I may: the post-commit email that the SCM system sends includes an author in the message body. Is there some way to get Jira to parse this out in order to automatically assign the merge-task to the author of the commit (rather than to the default assignee of the project in Jira)?
Cheers,
dan
Apr 16, 2008
Ian Daniel [Atlassian] says:
Hi Dan, Unfortunately there isn't a way for JIRA to do that. I'm not an expert ...Hi Dan,
Unfortunately there isn't a way for JIRA to do that. I'm not an expert on Subversion triggers, but I suggest you investigate if there is a way to have the triggered email being sent by the author of the commit.
Kind regards,
Ian
Apr 14, 2008
Matthew Beermann says:
I'd like for JIRA to send an email after a new Subversion commit appears for a p...I'd like for JIRA to send an email after a new Subversion commit appears for a particular issue. So far as I can tell, this would involve the plugin exposing an Event, and/or me creating a Listener, but I'm a little fuzzy on the details...
Thanks,
Matthew
Apr 14, 2008
Ian Daniel [Atlassian] says:
Hi Matthew, The Subversion plugin does not support this, and isn't going to: ht...Hi Matthew,
The Subversion plugin does not support this, and isn't going to: http://jira.atlassian.com/browse/SVN-91. As Anton indicates in that issue, you could use a Subversion trigger to achieve this.
Kind regards,
Ian
Apr 15, 2008
Matthew Beermann says:
That's not quite the same thing, though: Subversion doesn't know which users are...That's not quite the same thing, though: Subversion doesn't know which users are interested in a particular bug - only JIRA knows.
A related question: is there an (optional) way for the contents of the Subversion Commits pane to be included in the issue's RSS feed?
Apr 15, 2008
Ian Daniel [Atlassian] says:
Hi Matthew, Unfortunately the Subversion plugin does not allow you to include t...Hi Matthew,
Unfortunately the Subversion plugin does not allow you to include the contents of the Subversion Commits pane in the issue's RSS feed.
Kind regards,
Ian
Apr 28, 2008
Rizwan Kassim says:
I tried out this plugin, but moved to the Fisheye plugin instead. My star...I tried out this plugin, but moved to the Fisheye plugin instead.
My startup log still has
"2008-04-28 12:58:46,426 main ERROR [atlassian.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with name: Subversion Revision Indexing Service
com.atlassian.jira.service.ServiceException: Could not find class: com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService
at com.atlassian.jira.service.ServiceFactory.getService(ServiceFactory.java:36)"
How do I fully uninstall the plugin corretly?
Thanks!
Apr 28, 2008
Ian Daniel [Atlassian] says:
Hi Rizwan, Thanks for reporting this. I have reproduced the problem and raised ...Hi Rizwan,
Thanks for reporting this. I have reproduced the problem and raised it as a bug: http://jira.atlassian.com/browse/SVN-206.
The fix is to manually delete the Subversion Revision Indexing Service from Administration > Services.
Kind regards,
Ian
Apr 29, 2008
Gunnar Wagenknecht says:
Hi, We extended the Subversion plug-in with a report to list all changes to a f...Hi,
We extended the Subversion plug-in with a report to list all changes to a files within a version development cycle. http://jira.atlassian.com/browse/SVN-207
-Gunnar
May 05, 2008
Tobias Keller says:
Does version 0.10.3 of the Subversion Plugin work with the latest J...Does version 0.10.3 of the Subversion Plugin work with the latest JIRA version (3.12.3)?
Cheers,
Tobi
May 21, 2008
Ian Daniel [Atlassian] says:
Yes, it does.Yes, it does.
May 19, 2008
Bartosz Rakowski says:
Hi, I am experiencing following error: 2008-05-19 14:34:12,993 http-8080...Hi,
I am experiencing following error:
2008-05-19 14:34:12,993 http-8080-Processor18 ERROR [ext.subversion.projecttabpanels.SubversionProjectTabPanel] Error retrieving actions for project
java.lang.IllegalStateException: The connection to the repository is not active
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.getLogEntry(SubversionManagerImpl.java:161)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.getLogEntriesByProject(RevisionIndexer.java:661)
at com.atlassian.jira.plugin.ext.subversion.projecttabpanels.SubversionProjectTabPanel.getRecentCommits(SubversionProjectTabPanel.java:159)
at com.atlassian.jira.plugin.ext.subversion.projecttabpanels.SubversionProjectTabPanel.getHtml(SubversionProjectTabPanel.java:126)
at com.atlassian.jira.web.action.browser.Browser.getProjectTabHtml(Browser.java:366)
at sun.reflect.GeneratedMethodAccessor5864.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:61)
at webwork.util.InjectionUtils.invoke(InjectionUtils.java:52)
at webwork.util.ValueStack.findValue(ValueStack.java:426)
at webwork.util.ValueStack.findValue(ValueStack.java:175)
at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.java:61)
at webwork.view.taglib.BasicPropertyTag.doStartTag(BasicPropertyTag.java:54)
at org.apache.jsp.includes.panels.browser.tabpanels_jsp._jspx_meth_webwork_property_7(tabpanels_jsp.java:801)
at org.apache.jsp.includes.panels.browser.tabpanels_jsp._jspx_meth_webwork_else_3(tabpanels_jsp.java:774)
at org.apache.jsp.includes.panels.browser.tabpanels_jsp._jspService(tabpanels_jsp.java:306)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jsp.secure.views.browser.browseproject_jsp._jspService(browseproject_jsp.java:191)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:192)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:110)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:619)
I am accessing SVN through the tunnel on port 3690. Any suggestions?
May 21, 2008
Ian Daniel [Atlassian] says:
Hi Bartosz, It looks like the SVN plugin can't access your SVN repository. Your...Hi Bartosz,
It looks like the SVN plugin can't access your SVN repository. Your tunnelling is the first place to investigate. Try accessing the SVN repository from another SVN client from the same box that JIRA is installed on, to see if the problem is specific to the plugin or is a networking problem you need to resolve.
If you need further assistance, and if you have a current maintenance licence for JIRA, or if you are evaluating JIRA, can you please create an issue in our support system, https://support.atlassian.com, with the details of the problem, and we will investigate it.
Kind regards,
Ian
May 26, 2008
Bartosz Rakowski says:
Hi Ian, I did not have any problems with access to repository using Tortoise SV...Hi Ian,
I did not have any problems with access to repository using Tortoise SVN client (on the same box that JIRA is installed).
And i did create SVN-211
Best regards,
Bartosz Rakowski
May 26, 2008
Ian Daniel [Atlassian] says:
Hi Bartosz, Our support system is https://support.atlassian.com, not http://jir...Hi Bartosz,
Our support system is https://support.atlassian.com, not http://jira.atlassian.com. We have created a support case for you, https://support.atlassian.com/browse/JSP-23627, and resolved http://jira.atlassian.com/browse/SVN-211.
Kind regards,
Ian
May 27, 2008
Bartosz Rakowski says:
Hi Ian, Thanks for the support. I have enabled debug messages: log4j.category....Hi Ian,
Thanks for the support. I have enabled debug messages:
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console, filelog
log4j.additivity.com.atlassian.jira.plugin.ext.subversion = false
and after that, everything was clear. Sorry for trouble.
Best regards,
Bartosz Rakowski
May 27, 2008
Ian Daniel [Atlassian] says:
Hi Bartosz, Thanks for the update, and I'm glad the problem is sorted. Kind re...Hi Bartosz,
Thanks for the update, and I'm glad the problem is sorted.
Kind regards,
Ian
Jul 13, 2008
Jana Frary says:
The 0.10.3 zip file attached doesn't have the javasvn and ganymed jars in it. Ho...The 0.10.3 zip file attached doesn't have the javasvn and ganymed jars in it. However, the instructions say I need to replace them. Do I not need to replace them?
Jul 14, 2008
David Chui says:
Hi Jana, You'll only need to replace the jars if they are there. The javasvn an...Hi Jana,
You'll only need to replace the jars if they are there. The javasvn and ganymed jars are listed because older versions of this plugin ships with them.
I've also added a note on the removal of JARs from JIRA's WEB-INF/lib directory.
Jul 15, 2008
Chris Tashjian says:
We recently updated our SVN server to 1.5.0 and this plugin has stopped working....We recently updated our SVN server to 1.5.0 and this plugin has stopped working. Is there a workaround for this (Jira 3.12.2 and plugin version 0.10.3)? Here's the error message:
An error occured while activating the connection: svn: Malformed network data.
EDIT: I see there's already an issue for this - http://jira.atlassian.com/browse/SVN-217
I just updated my SVN Kit jar in Jira to 1.1.8 and it's fixed...
Jul 28, 2008
Yann FOUBERT says:
I also did this operation and it works fine for existing repositories. The prob...I also did this operation and it works fine for existing repositories.
The problem is with newly created repositories:
We get the error:
2008-07-28 16:57:39,894 http-8080-Processor5 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository file:///F:/SVN_Repositories/ArteCPP failed: org.tmatesoft.svn.core.SVNException: svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///F:/SVN_Repositories/ArteCPP'
svn: Expected FS format '2'; found format '3'
org.tmatesoft.svn.core.SVNException: svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///F:/SVN_Repositories/ArteCPP'
svn: Expected FS format '2'; found format '3'
To correct this, I had to use the latest beta release of the svn kit: 1.2.0-beta4
Aug 01, 2008
Alex Broad says:
We have been running this plugin for a few years - in different versions all wit...We have been running this plugin for a few years - in different versions all with no problems - it has been working great.
however it stopped working some months ago now and today is the first chance we have had in taking down jira
any ideas what this error is about
*****************************************************************************************************
JIRA 3.9.1 build: 234 (Enterprise Edition) started. You can now access JIRA through your web browser.
*****************************************************************************************************
2008-08-01 19:21:37,363 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] RevisionIndexer.createIndexIfNeeded()
2008-08-01 19:21:37,363 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] RevisionIndexer.createIndexIfNeeded()
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] repos size = 5
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] repos size = 5
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating revision index for repository=91d06709-ebff-0310-94a1-97b3be112118http://svn.xxxxxxxxxxxx.com/svn/product_maintenance
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating revision index for repository=91d06709-ebff-0310-94a1-97b3be112118http://svn.xxxxxxxxxxxx.com/svn/product_maintenance
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating last revision indexed.
2008-08-01 19:21:37,366 JiraQuartzScheduler_Worker-2 DEBUG [ext.subversion.revisions.RevisionIndexer] Updating last revision indexed.
2008-08-01 19:21:37,380 JiraQuartzScheduler_Worker-2 ERROR [atlassian.jira.service.ServiceRunner] Error occured while executing the service [ Container: com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService This service indexes Subversion revisions. delay [3600000ms]]
java.lang.NoSuchFieldError: log
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.run(RevisionIndexService.java:38)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Thanks
To add to this we are running Version JIRA 3.9.1 build: 234 and subversion Plugin Version: 0.9.11 Jira Versions: 3.8 - 3.1
Aug 08, 2008
JP Patrikainen says:
Hi, I just installed svn plugin and it is create tool for configuration m...Hi,
I just installed svn plugin and it is create tool for configuration management.
I am just wondering.. do we have a possible security issue?
Is it possible to make subversion comment to wrong project by using another project's issue key value? Is it possible to connect repository to one or to only selected projects? I did not find it from this page (most cases I am blind).
Thank already,
-JP
BTW: that version support table is a little bit confusing.. 0.10.3 supports only 3.12.2?
Aug 29, 2008
Marie-Eve Racicot says:
Hi, I've installed the plugin successfully (or so I think) and see the Subvers...Hi,
I've installed the plugin successfully (or so I think) and see the Subversion control tab within the issues. However, I do not see the svn commit information, not even for the atlassian repository. I looked at the logs and do not see any errors however, I noticed that the INDEX$/plugins/atlassian-subversion-revisions does not exist in theJIRA installation.
I've stoped and restarted the JIRA service and it still doesn't exist. Do I have to wait an hour before it shows up? Strangely, when i did try the installation of the plugin on my own JIRA-test installation, it worked perfectly right away.
Any idea?
Aug 29, 2008
blah says:
With the SVN integration is it possible to set an issues status to resolved when...With the SVN integration is it possible to set an issues status to resolved when a fix is committed?
Sep 05, 2008
Jose Muanis F. Castro says:
Hi, I've just installed JIRA 3.12.3, with subversion plugin version 0.10....Hi,
I've just installed JIRA 3.12.3, with subversion plugin version 0.10.4, and I'm receiving a message in the log file wich is preventing it from working correctly.
2008-09-05 19:00:52,016 http-xx.xx.xx.xx-8007-Processor23 ERROR [subversion.issuetabpanels.changes.SubversionRevisionsTabPanel] Error retrieving actions for : PCONT-160
java.lang.NoSuchMethodError: com.atlassian.jira.issue.changehistory.ChangeHistoryManager.getPreviousIssueKeys(Ljava/lang/Long;)Ljava/util/Collection;
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.createQueryByIssueKey(RevisionIndexer.java:912)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.getLogEntriesByRepository(RevisionIndexer.java:515)
at com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.SubversionRevisionsTabPanel.getActions(SubversionRevisionsTabPanel.java:36)
at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelModuleDescriptor.getActions(IssueTabPanelModuleDescriptor.java:99)
at com.atlassian.jira.web.action.issue.ViewIssue.getActions(ViewIssue.java:400)
Running in JDK 1.5.0_11
Any toughts on this?
muanis
Sep 12, 2008
Dan Dunham says:
I'm having this exact same problem running JIRA 3.12.3 and 0.10.4. The Exceptio...I'm having this exact same problem running JIRA 3.12.3 and 0.10.4. The Exception occurs when I click on the "Subversion Commits" tab for any issue.
Sep 12, 2008
Oleksii Shurubura says:
Downgrade to 0.10.3 plugin version as JIRA 3.12.x works only with 0.10.3. PS: i...Downgrade to 0.10.3 plugin version as JIRA 3.12.x works only with 0.10.3.
PS: if you'd like to support svn 1.5. download svnkit 1.2.0rc2, copy svnkit.jar + trilead.jar and remove old svnkit-1.1.6.jar + trilead-ssh2-build211.jar
Sep 13, 2008
Dan Dunham says:
That did the trick. Thanks!That did the trick. Thanks!
Sep 23, 2008
Vishwajeet Singh says:
Hi, I am trying to setup Subversion plugin 0.10.3 with JIRA 3.12.3 and getting ...Hi,
I am trying to setup Subversion plugin 0.10.3 with JIRA 3.12.3 and getting following error
svn: PROPFIND request failed on '/trial/repo' svn: Connection refused: connect
Error occurred while creating the repository. Please refer to the log for more details.
It was working fine with 3.12; any ideas what could be the cause of problem??
Oct 02, 2008
Sam Byrd says:
Your URL above for pulling the source is incorrect. It should be: h...Your URL above for pulling the source is incorrect. It should be:
http://svn.atlassian.com/svn/public/contrib/jira/subversion-jira-plugin/tags/atlassian-jira-subversion-plugin-0.10.4
Nov 07, 2008
Amit Narayanan says:
In addition, your JAR download URL is incorrect as well. It seems to point...In addition, your JAR download URL is incorrect as well. It seems to point to the zipped up src for version 0.10.5.Oye.. nevermind. Its all there somewhere in that zip. Or maybe someone changed it since i last looked. Or maybe I didn't really look.
Oct 15, 2008
Jeryl Cook says:
Hi, Just a simple question, seriously :0, we have JIRA with the plugin working ...Hi,
:0, we have JIRA with the plugin working very nicely...however we have Tortoisesvn as a client to subversion, from their docs we just can't figure out
Just a simple question, seriously
which params to modify for each of the properties for the web.linking...can someone who has TortoiseSVN working with weblinkingn for JIRA please post a sample of their configuration???
Thanks!
Nov 03, 2008
Frank Stiller says:
Tortoise is a "Rich"-Client for SVN (so long we have the same understanding ), i...Tortoise is a "Rich"-Client for SVN (so long we have the same understanding
), i just cant figure out what you want to achieve by doing any integration in JIRA for it. The SVN-Webpresence will have nothing to do with Tortoise, have it? You will have to link to the Web-Presence of Subversion, what ever that will be at your company.
Nov 03, 2008
Wang Jinxing says:
Hi, I am trying to Subversion plugin 0.10.4 with JIRA 3.13 and getting followin...Hi,
I am trying to Subversion plugin 0.10.4 with JIRA 3.13 and getting following error. I don't know why.
Nov 12, 2008
Joe Goldberg says:
Hello, This plugin is working great, thanks for making it! I have on...Hello,
This plugin is working great, thanks for making it!
I have one question. Frequently, developers forget to add the bug ID in their commit messages, so we'd like to be able to later add a comment to the bug saying "Oops, this was fixed in Revision 123". Can the plugin automatically link "Revision 123" to a websvn page?
Thanks,
Joe
Dec 04, 2008
Emmanuel EUGENE says:
Hello, Really nice, thanks for your work. Which value of the Subversion Revis...Hello,
Really nice, thanks for your work.
Which value of the Subversion Revision Indexing Service delay should be relevant regarding to the performance of the plugin ? I suppose it depends on the size of the SVN repository ? I'd like to set it up to 1 minute but I can't say if it will be relevant in a production environment...
Someone idea ?
Dec 08, 2008
Piotr Stawiński says:
Hi When i'm adding new repository i have an error : Errors svn: PROPFIND requ...Hi
When i'm adding new repository i have an error :
Errors
When i type this address http://my_serv:8080/svnbook into my websitebrowser i see my svn repository.
Please for help and thanks for all answears.
Best regards
Piotr Stawiński
Dec 17, 2008
Chris R says:
Is it possible to force the plugin to re-index from a particular starting revisi...Is it possible to force the plugin to re-index from a particular starting revision? Specifically, I've updated some older log messages to include references to JIRA issues, but since they were indexed some time ago, they're not showing up here.