Properties used by kdesvn for configuration

Bugtracker integration

The TortoiseSVN project designed a nice property system for integrating bugtracker into subversion GUI. This moment kdesvn doesn't support extra fields in commit box (will follow later) and doesn't understand all but following properties:

Table 2.1. Bugtracker Integration Properties

Property Description Example

bugtraq:url Holds the url to bugtracker. It has to contain the %BUGID% marker. http://kdesvn.alwins-world.de/ticket/%BUGID%

Property	Description	Example
`bugtraq:url`	Holds the url to bugtracker. It has to contain the `%BUGID%` marker.	http://kdesvn.alwins-world.de/ticket/%BUGID%
`bugtraq:logregex`	Contains one or two regular expressions, separated by a newline. If only one expression is set, then the bare bug ID's must be matched in the groups of the regex string. If two expressions are set, then the first expression is used to find a string which relates to the bug ID but may contain more than just the bug ID (e.g. "Issue #123" or "resolves issue 123"). The second expression is then used to extract the bare bug ID from the string extracted with the first expression. Please keep care about not wanted spaces after the regular expression and don't forget the brackets around the number description.	Single (useable with TRAC): #(\d+) Now all numbers like `#190` will parsed and translated to an url in logoutput. Two expressions: [Ii]ssue #?(\d+)(,? ?#(\d+))* (\d+) Remember: Keep care of white spaces after the `(\d+)`! This is one of the most errors while this expressions doesn't match!

bugtraq:logregex

Contains one or two regular expressions, separated by a newline.

If only one expression is set, then the bare bug ID's must be matched in the groups of the regex string. If two expressions are set, then the first expression is used to find a string which relates to the bug ID but may contain more than just the bug ID (e.g. "Issue #123" or "resolves issue 123"). The second expression is then used to extract the bare bug ID from the string extracted with the first expression.

Please keep care about not wanted spaces after the regular expression and don't forget the brackets around the number description.

Single (useable with TRAC):

#(\d+)

Now all numbers like #190 will parsed and translated to an url in logoutput.

Two expressions:

[Ii]ssue #?(\d+)(,? ?#(\d+))*
(\d+)

Remember: Keep care of white spaces after the (\d+)! This is one of the most errors while this expressions doesn't match!

On local opened repositories (eg., file://-Protocoll) and on working copies this properties will searched upward from opened folder until found or the subversion-toplevel is reached. On repositories opened via network (all except file:// protocoll) it is only searched on opened folder itself.

Support for multiple sets of this properties may follow later, (eg., in subfolder extra values for other tracker etc.) but in most cases evaluatin single tracker links should be enough.

Prev	Contents	Next
Other Operations	Up	The revision tree