[gurtle] r240 committed - Fixed issue #57

[gur...@googlecode.com]

Revision: 240
Author: azizatif
Date: Mon Oct 14 18:30:59 2013 UTC
Log: Fixed issue #57
http://code.google.com/p/gurtle/source/detail?r=240

Modified:
/wiki/IssueUpdateSetup.wiki
/wiki/Parameters.wiki
/wiki/ProjectDescription.wiki

=======================================
--- /wiki/IssueUpdateSetup.wiki Mon Jun 1 08:51:26 2009 UTC
+++ /wiki/IssueUpdateSetup.wiki Mon Oct 14 18:30:59 2013 UTC
@@ -1,6 +1,6 @@
#summary How to setup issue updates

-Starting with version 0.5, Gurtle can automatically close issues with a
reference to the revision number when you make a commit via TortoiseSVN
(1.6 or later). Since
[http://code.google.com/p/support/issues/detail?id=148 Google Code does not
have an API to its issue tracker yet], Gurtle uses a backdoor means to
update issues by doing an HTML form submission, much the same way a person
would do it through the project web site. The downside of this approach is,
however, that Google Code can change the form processing and break Gurtle.
To avoid having everyone update their Gurtle installation each time this
happens, the form submission has not been hard-wired into Gurtle. Instead,
Gurtle expects an external script to carry out this task and which can be
updated independently and even maintained by the community.
+Starting with version 0.5, Gurtle can automatically close issues with a
reference to the revision number when you make a commit via TortoiseSVN
(1.6 or later) and TortoiseGit. Since
[http://code.google.com/p/support/issues/detail?id=148 Google Code does not
have an API to its issue tracker yet], Gurtle uses a backdoor means to
update issues by doing an HTML form submission, much the same way a person
would do it through the project web site. The downside of this approach is,
however, that Google Code can change the form processing and break Gurtle.
To avoid having everyone update their Gurtle installation each time this
happens, the form submission has not been hard-wired into Gurtle. Instead,
Gurtle expects an external script to carry out this task and which can be
updated independently and even maintained by the community.

To enable the issue update UI in Gurtle, start by downloading the latest
version of the script by exporting
http://gurtle.googlecode.com/svn/scripts/ using a Subversion client like
TortoiseSVN.

@@ -12,7 +12,7 @@

Prepend `updissue.cmd` with the path where you exported the scripts
earlier.

-That's it! Next time you make a commit via TortoiseSVN and use Gurtle to
select one or more issues, you will see a dialog box like the following
show up _after_ the commit and using which you will be able to set the
comment and status for each issue.
+That's it! Next time you make a commit via TortoiseSVN/TortoiseGit and use
Gurtle to select one or more issues, you will see a dialog box like the
following show up _after_ the commit and using which you will be able to
set the comment and status for each issue.

If you start finding that you are getting errors during issue updates,
make sure to check back and see if there is a new version of the script
available. You are also encouraged to leave the `--debug` flag that could
aid in identifying and [http://code.google.com/p/gurtle/issues/entry
reporting issues].

=======================================
--- /wiki/Parameters.wiki Sun Jan 2 14:41:38 2011 UTC
+++ /wiki/Parameters.wiki Mon Oct 14 18:30:59 2013 UTC
@@ -3,6 +3,8 @@

= Parameters =

+(These instructions mainly apply to ToroiseSVN. For TortoiseGit, see
[http://tortoisegit.org/docs/tortoisegit/tsvn-dug-bugtracker.html 3.34.
Integration with Bug Tracking Systems / Issue Trackers])
+
Once you have Gurtle installed on your system, there are two ways to
enable it in TortoiseSVN (TSVN) for a given Google Code project. If you are
using TSVN 1.5 then the parameters have to be configured manually in TSVN
Settings for each working copy and this has to be done by each member of
the project on his or her workstation(s). If you are using TSVN version 1.6
or later then you can set the Gurtle and TSVN configuration in properties
in the project's Subversion repository once. Each project member will then
simply inherit the settings by checking out or updating their working copy
and Gurtle will be automatically enabled for the project in TSVN.

The parameters for Gurtle is a semi-colon delimited list of name and value
pairs where the name and value within each pair is separated by an equal
(=) sign. The syntax can be summarized as follows:
@@ -51,3 +53,4 @@

$ svn commit -m "Added TSVN/Gurtle IBugTraqProvider properties."
}}}
+
=======================================
--- /wiki/ProjectDescription.wiki Sun Mar 29 17:58:42 2009 UTC
+++ /wiki/ProjectDescription.wiki Mon Oct 14 18:30:59 2013 UTC
@@ -1,8 +1,8 @@
#summary Project description as it appears on the project home page

-Gurtle is a [http://tortoisesvn.net/ TortoiseSVN] issue tracker plug-in
(an
[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ibugtraqprovider.html
IBugTraqProvider] implementation) for [http://code.google.com/hosting
projects hosted at Google Code].
+Gurtle is a [http://tortoisesvn.net/ TortoiseSVN]/[http://tortoisegit.org/
TortoiseGit] issue tracker plug-in (an
[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ibugtraqprovider.html
IBugTraqProvider] implementation) for [http://code.google.com/hosting
projects hosted at Google Code].

-With release 1.5, TortoiseSVN introduced the possibility for anyone to
author a COM-based plug-in that enables a user to query a project's issue
tracking system during a commit. Gurtle is such a plug-in and enables the
user to consult issues of a project hosted by Google Code from within the
[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-commit.html#tsvn-dug-commit-basics
TortoiseSVN Commit dialog box]. The screenshot below shows how the issue
dialog box looks like in Gurtle for the [http://code.google.com/p/support/
project hosting support] project.
+With release 1.5, TortoiseSVN (and TortoiseGit later) introduced the
possibility for anyone to author a COM-based plug-in that enables a user to
query a project's issue tracking system during a commit. Gurtle is such a
plug-in and enables the user to consult issues of a project hosted by
Google Code from within the
[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-commit.html#tsvn-dug-commit-basics
TortoiseSVN Commit dialog box]. The screenshot below shows how the issue
dialog box looks like in Gurtle for the [http://code.google.com/p/support/
project hosting support] project.

http://gurtle.googlecode.com/svn/wiki/SupportIssues.png

@@ -24,7 +24,7 @@

== Requirements ==

- * [http://tortoisesvn.net/downloads TortoiseSVN] version 1.5 or later
+ * [http://tortoisesvn.net/downloads TortoiseSVN] or
[http://tortoisegit.org/ TortoiseGit]
*
[http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
Microsoft .NET Framework 2.0]
* Any Windows version where TortoiseSVN and Microsoft .NET Framework 2.0
are supported though most testing has been conducted on Windows XP and
Vista.
* Internet connection for reaching Google Code