[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: New Issue Tracker for TortoiseSVN

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 21 Oct 2009 19:56:19 +0200

On 21.10.2009 18:31, Johann Moro wrote:
> I might as well carry on answering my own questions.
>
> After much trial and error I understand what I did wrong. When I set the
> path I thought it didn't matter what directory I provided... but it
> looks like it does and I don't understand why.
>
> From the spec, I now understand that it's looking for the *working*
> copy. Why am I supposed to enter a working copy here?
> Does that mean that I need to enter one configuration per working copy I
> have on disk? I have dozens of working copies and they don't always live
> under the same path.
>
> Also It looks like it doesn't have to be a working copy to work but it
> has to be a root path to where I'm committing from. For instance if my
> working copy is in D:\Dev\SVN\MyWorkingCopy, it will work if I set the
> path to D:\ but not if I set the path to C:\
>
> I'm a bit puzzled about why it behaves like this

Very simple: you can have multiple working copies, which use different
issue trackers and therefore different plugins. So you have to specify
the path for which your plugin is responsible.

But you can also set the bugtraq:provideruuid property on your working
copies.

Just make sure that you use your own uuid for your COM object! Otherwise
all hell breaks lose.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2409884
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-21 19:56:29 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.