| Name | JIRA Subversion Plugin |
|---|---|
| Vendor | Atlassian Pty Ltd (Website) |
| Authors | Mike Cannon-Brookes, Dylan Etkin |
| Homepage | http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin |
| Issue Management | http://developer.atlassian.com/jira/browse/SVN |
| Continuous Integration | n/a |
| Categories | Remote Access |
| Most Recent Version | 0.10.4.2 |
| Availability | JIRA v3.13 to v3.13 |
| State | Stable |
| Support |
|
| License | Freeware / Open Source (BSD) |
| Price | Free |
| Release Docs | http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin |
| Java API Docs | n/a |
| Download Source | http://svn.atlassian.com/svn/public/contrib/jira/subversion-jira-plugin/tags/atlassian-jira-subversion-plugin-0.10.4.2/ |
| Download JAR | atlassian-jira-subversion-plugin-0.10.4.2.zip |
Compatibility With JIRA
| Plugin Version | 3.2.x | 3.3.x | 3.4.x | 3.5.x | 3.6 | 3.7-beta2 | 3.7.x | 3.8.x | 3.9 | 3.10 | 3.11 | 3.12.2 | 3.13 | Tested | Supported |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0.6.1 |  |
||||||||||||||
| 0.7.1 | |
||||||||||||||
| 0.8.2 | |
||||||||||||||
| 0.9.1 | |
||||||||||||||
| 0.9.2 | |
||||||||||||||
| 0.9.3 | |
||||||||||||||
| 0.9.4 | |
||||||||||||||
| 0.9.5 | |
||||||||||||||
| 0.9.6 | |
||||||||||||||
| 0.9.7 | |
||||||||||||||
| 0.9.8 | |
||||||||||||||
| 0.9.9 | |
||||||||||||||
| 0.9.11 | |
|
|||||||||||||
| 0.9.12 | |
||||||||||||||
| 0.10.0 |  |
|
Daniel Petzen (Feb/29/2008) | ||||||||||||
| 0.10.1 | |
|
|
David Chui (Jan/29/2008) | |||||||||||
| 0.10.2 | |
|
|
David Chui (Mar/25/2008) | |||||||||||
| 0.10.3 | |
|
|
David Chui (Apr/03/2008) | |||||||||||
| 0.10.4 | |
|
|
|
Brad Baker (Sep/02/2008) | ||||||||||
| 0.10.4.1 | |
|
|
|
David Chui (Jan/21/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
Screenshots |
||
|---|---|---|
|
|
|
|
|
|
|
Screenshot of the plugin in action.
|
pic
|
|
|
||
Notes
By default, the subversion index will refresh every 1 hour, this means that you may not see your changes in Jira immediately. You can edit how often the service runs by editing the delay from Administration -> System -> Services.
Special thanks to the TMate JavaSVN library - it has made the development of this plugin a lot easier
Install Instructions
(further notes in the README.txt inside the download)
1. Copy files
- Copy the following jar files from the distribution's lib/ directory into JIRA's WEB-INF/lib. If you are upgrading the plugin, make sure you delete the old ones from WEB-INF/lib first.
- atlassian-subversion-plugin-*.jar
- javasvn-*.jar (if any)
- svnkit-*.jar (if any)
- ganymed-*.jar (if any)
- trilead-*.jar (if any)
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.
- Finally, to see everything the Subversion plugin does (on startup), edit JIRA's log4j.properties, and add the lines:
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console, filelog log4j.additivity.com.atlassian.jira.plugin.ext.subversion = false
- Double-check that you have set jira.option.ignore.url.with.key=false in jira-application.properties.
If you make any configuration changes, please delete the $INDEXDIR/plugins/atlassian-subversion-revisions directory and restart JIRA to make the change take effect.
Support / Bug Reports / Feature Suggestions
If you have an installation problem or a question please check the debugging checklist above and create a support requestif that doesn't help. If you have found a bug or would like to raise a new feature request please file a JIRA issue online in the Subversion JIRA plugin project.
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.
Version History
Plugin Versions
| Version | Date | State | License | Price |
0.10.4.2
(#7)
|
05 Feb 2009 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.4.1
(#6)
|
21 Jan 2009 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.4
(#5)
|
01 Sep 2008 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.3
(#4)
|
03 Apr 2008 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.2
(#3)
|
24 Mar 2008 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.1
(#2)
|
06 Feb 2008 | Stable | Freeware / Open Source (BSD) | Free |
|
0.10.0
(#1)
|
06 Feb 2008 | Stable | Freeware / Open Source (BSD) | Free |
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 (301)
Nov 18, 2004
Brendan Doherty says:
Here is my apache log for the requests from JIRA, could anyone tell me if it is ...Here is my apache log for the requests from JIRA, could anyone tell me if it is working correctly? it doesnt seem to be picking up the commit messages, but it doesnt throw any errors either?
"note: the first time the service runs it will take a while to index all of your existing issues - be patient" - How long is a while 2/3 hours more?
IP - username [18/Nov/2004:17:19:37 +0000] "PROPFIND /repos HTTP/1.1" 207 641
IP - username [18/Nov/2004:17:19:37 +0000] "PROPFIND /repos/!svn/vcc/default HTTP/1.1" 207 392
IP - username [18/Nov/2004:17:19:38 +0000] "PROPFIND /repos/!svn/bln/6 HTTP/1.1" 207 443
Nov 18, 2004
Mike Cannon-Brookes says:
Brendan, If you turn up the logging level in JIRA you should see more informati...Brendan,
If you turn up the logging level in JIRA you should see more information from the plugin.
The easiest way to do this is to edit WEB-INF/classes/log4j.properties within the web application and add something like:
log4j.category.com.atlassian.jira.plugin.ext.subversion = DEBUG, console log4j.category.com.atlassian.jira.plugin.ext.subversion.additivity = falseThat should enable all debug logging from the Subversion plugin, which will tell you what it is trying to retrieve from your Subversion server, which changes it matched to issues etc.
Let us know how you go.
Cheers,
Mike
Oct 28, 2007
AJ says:
<b> Hi , Is there a way to hide the 'Subversion Commit' tab from Users. We...<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!
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)