The easiest would be to submit a patch.
I believe all the logic is in the following method, which is sitting in
org.tigris.subversion.subclipse.ui plugin:
org.tigris.subversion.subclipse.ui.settings.ProjectProperties.getLinkList(String
commitMessage)
You may also need to update few other methods. Eg.
org.tigris.subversion.subclipse.ui.settings.ProjectProperties.getProjectProperties(IResource
resource)
If you need help in configuring dev environment you can look at the last
section in my article at http://dev2dev.bea.com/lpt/a/453
regards,
Eugene
Greg Irvine wrote:
>
> To follow up on a thread from August where Mark said that
> bugtraq:logregex wasn’t implemented for various reasons including the
> fact no-one had asked for it.
>
> So, Mark, now that I’m using these tracking features I’d love to have
> the logregex working because I need to vary where my URL needs to go
> depending on some keywords in the bug id, and logregex seems to be the
> only way I can do that (by returning the BUGID as the full URL rather
> than as just the #). Some change requests are bugs and some are
> evolutions and these two things are stored in different “databases”.
>
> So, if it’s not too much of hassle, it would be great to see it in an
> up-coming release.
>
> Thanks and regards,
>
> Greg.
>
> ps. As discussed last week, I was having troubles with not getting the
> ID textfield, then I fixed it, but now I’m not getting it again for
> the same folder. Kind of weird. I’ll keep plugging away.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Oct 1 05:41:02 2006