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

Re: [Subclipse-users] Blame (annotate) issues in subclipse 1.4.3

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 14 Aug 2008 13:46:23 -0400

On Wed, Aug 13, 2008 at 5:08 PM, Gene Gorokhovsky
<ggorokhovsky_at_apriori.com> wrote:
> After upgrading to svn 1.5.x and subclipse 1.4.x we are having issues with
> team annotate.

When you tested from the command line are you 100% certain you used
the SVN 1.5.1 command line? In theory, it should be possible to
provide "some" set of command line options that gives the same error.
I'll take a look at the JavaHL code in Subversion though to see if
they have some parameters flip-flopped or something. If that were the
case, it would seem unlikely that SVNKit would have the same problem
though. Anyway, I will keep digging on that front.

When I look at our code, the only option I see that we have to provide
to the API that is "ambiguous" to the command line is that we have to
support a start and end revision. The end revision value is what you
see in the command line, for the start revision we provide a constant,
Revision.START which I assume translates into 0 or something.

It also seems odd that you seem to get this on all files, where as I
do not get it on any. Is there anything about your repository history
that could be triggering a bug? Such as the paths being moved/renamed
during their lifetime? I'd expect any bugs caused by that to show up
in the SVN command line code too though.

Can you please file a bug in our issue tracker?

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-14 19:46:52 CEST

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