You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Edward Knoll <ed...@fedex.com> on 2010/05/07 21:31:01 UTC
Is there any way of extending the set of keywords recognized/expanded by Subversion?
Our company is integrating Subversion into a larger process environment,
and there are now other kinds of artifacts identifiers associated with
our repository which are outside of Subversion. It would be handy if
there were a way to extend the set of keywords recognized/expanded by
Subversion to include these external artifact identifiers.
Re: Is there any way of extending the set of keywords
recognized/expanded by Subversion?
Posted by Erik Huelsmann <eh...@gmail.com>.
Hi,
On Mon, May 10, 2010 at 7:33 PM, Ryan Schmidt
<su...@ryandesign.com> wrote:
>
> On May 10, 2010, at 09:07, Edward Knoll wrote:
>
>> Not Subversion source control, but some custom SCM/bookkeeping that has been built around/on top of Subversion - layers application teams don't have direct access. My (forlorn) hope is there's a way of extending the keywords, so the application team could reference these other bookkeeping artifacts as embedded keywords and the process/SCM extensions could set those new keywords.
>
> Sorry, there isn't any way of doing that, short of modifying the Subversion source code and using your own custom Subversion builds.
Right. There's a patch (in our issue tracker) to support the same
thing for FreeBSD:
http://subversion.tigris.org/issues/show_bug.cgi?id=890
Bye,
Erik.
Re: Is there any way of extending the set of keywords recognized/expanded by Subversion?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 10, 2010, at 09:07, Edward Knoll wrote:
> Not Subversion source control, but some custom SCM/bookkeeping that has been built around/on top of Subversion - layers application teams don't have direct access. My (forlorn) hope is there's a way of extending the keywords, so the application team could reference these other bookkeeping artifacts as embedded keywords and the process/SCM extensions could set those new keywords.
Sorry, there isn't any way of doing that, short of modifying the Subversion source code and using your own custom Subversion builds.
RE: Is there any way of extending the set of keywords recognized/expanded by Subversion?
Posted by Edward Knoll <ed...@fedex.com>.
Not Subversion source control, but some custom SCM/bookkeeping that has been built around/on top of Subversion - layers application teams don't have direct access. My (forlorn) hope is there's a way of extending the keywords, so the application team could reference these other bookkeeping artifacts as embedded keywords and the process/SCM extensions could set those new keywords.
-----Original Message-----
From: Bob Archer [mailto:Bob.Archer@amsi.com]
Sent: Friday, May 07, 2010 4:19 PM
To: Edward Knoll; users@subversion.apache.org
Subject: RE: Is there any way of extending the set of keywords recognized/expanded by Subversion?
> Our company is integrating Subversion into a larger process environment,
> and there are now other kinds of artifacts identifiers associated with our
> repository which are outside of Subversion. It would be handy if there
> were a way to extend the set of keywords recognized/expanded by Subversion
> to include these external artifact identifiers.
Not that I am aware of. Here we use our build scripts to inject stuff like this into the projects and source. The values probably aren't specific to source control I assume?
BOb
RE: Is there any way of extending the set of keywords
recognized/expanded by Subversion?
Posted by Bob Archer <Bo...@amsi.com>.
> Our company is integrating Subversion into a larger process environment,
> and there are now other kinds of artifacts identifiers associated with our
> repository which are outside of Subversion. It would be handy if there
> were a way to extend the set of keywords recognized/expanded by Subversion
> to include these external artifact identifiers.
Not that I am aware of. Here we use our build scripts to inject stuff like this into the projects and source. The values probably aren't specific to source control I assume?
BOb