On 10/12/07, Stefan Küng <firstname.lastname@example.org> wrote:
> Mark Phippard wrote:
> >> You're right, there's no way to answer the question "which revisions
> >> reference issue 123". But issuetrackers which have direct access to the
> >> repository can modifiy or read revision properties much easier than log
> >> messages (no need to parse them).
> > True. I suspect most have gone the hook script route though, where
> > they store this in the issue tracker. The performance wouldn't scale
> > to get it from SVN.
> I don't know about the performance, but I suspect it would be slightly
> faster to just read a property than to read a (maybe) long log message
> and parse it.
No, I agree it would always be easier than log messages. I meant if
you really need to know the revisions for an issue the only way that
scales is a hook script that stores that information in the issue
> > I'll ultimately do my best to support what you decide. Subclipse
> > might not get this until 1.6 though as none of these API's are exposed
> > via JavaHL and I think the clock has pretty much run out on getting
> > some of this (in terms of JavaHL). I think that is OK though, as you
> > have often had features ahead of us for a release.
> Well, I don't like to just decide about features that affect other
> clients as well. That's why we have this discussion ;)
> But are you sure about the API's not being available in JavaHL? The
> setting of revision properties is done by filling a hash table in the
> client context struct which you must pass anyway (the hash table is set
> to NULL if it's not used, which is the default).
The "HL" stands for high-level. Basically, most of the low level
details are hidden away (implemented in the C++ side that the Java
calls via JNI). So new API's have to be exposed. The one to set rev
props as part of the commit, and also the new one to query them are
both not currently exposed.
Doing so is never terribly hard, just a lot of JNI grunt work that
only a couple of the committers know how to do.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 12 23:54:59 2007