RE: Re: Re: [Subclipse-users] Support for bugtraq:logregex
Date: Tue, 28 Apr 2009 01:37:19 -0700 (PDT)
> Sounds like a bug?
As a background information, my company was already using TortoiseSVN and this logregex feature. I'm now trying to set-up a common development process using eclipse, mylyn and subclipse among other things, and I don't want to remove or change the properties that already exist in our repositories.
Regarding the problem itself, I just created an empty repository to test the logregex feature by comparing the way subclipse and TortoiseSVN behave. I only added the trunk folder with the following properties:
bugtraq:logregex issue# (\d+)
With this config, the input field "Issue Number" is still displayed in the subclipse commit window. This is a first difference with TortoiseSVN, but it's not the end of the world.
However, if I enter a log message containing a valid bug-id (for example, issue# 345), the issue number is taken into account in the "History view" and "Open bug URL" works properly.
Then, if I add the property:
And try to commit with a valid bug-id in the log message, I get the warning "Issue Number: has not been entered. Do you wish to commit anyway?", which is a second difference and a (ok, small) problem from my point of view.
Since I use the "Commit comment template" feature provided by Mylyn to automatically insert the correct task number in the log message, it's a little bit frustrating to have this warning displayed each time I make a commit :)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
This is an archived mail posted to the Subclipse Users mailing list.