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

Re: bugtraq properties and multiple project URLs

From: Dirk <tortoisesvn_at_nogga.de>
Date: Thu, 25 Sep 2014 17:14:12 +0200

Hi Gavin

Am 25.09.2014 00:42, schrieb Gavin Lambert:
> On 25/09/2014 03:13, Dirk wrote:
>> I'm now struggeling setting up the bugtraq properties, since I have to
>> switch the bugtraq:url depending on the character. It seems, that the
>> only possibility is point the bugtrq:url to a "switch board" url, that
>> will decode the link into the correct trac instance.
> The bugtraq properties don't have to be on the root. If you have subfolders in the repository for each project then you can set up the properties on these subfolders and they will apply as you'd expect provided that the log/commit operation is being done on the subfolder (or a grandchild) rather than the root.

Thanks, that is how we worked in the past. Works perfectly.
Now we have started to use one "common" folder, where source code from
both projects is mixed with each other. Over the long run, this new
folder will probably melt down into its own project with it's own
tracking. But for the next half year, we will continue to use the two
main projects for project tracking and will share source code in an easy
way within this folder. I know, not a perfect situation, but currently
the best we can do to not double the effort on the project tracking side.

After some further digging in the tortoiseSVN source code, the easiest
solution seems to be to open a new trac instance that serves as an
aggregation project and to write a plugin that will implement the switch
board.

Thanks
Dirk

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3089045

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-09-25 17:14:26 CEST

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

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