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

Re: JavaHL logMessages only one callback

From: Branko Čibej <brane_at_wandisco.com>
Date: Wed, 19 Aug 2015 11:04:53 +0200

On 19.08.2015 10:48, corneil.duplessis_at_gmail.com wrote:
> I am trying to find change history and thought that using logMessage will
> provide the information.
>
> I am using a call as descibre below:
>
> pegRevision = Revision.HEAD,
> ranges = [RevisionRange(Revision.HEAD, Revision.START)]
> stopOnCopy = false
> discoverPath = true
> includeMergedRevisions = true
> props = [REV_LOG, REV_DATE, REV_AUTHOR]
> limit = -1
>
> May callback function is only called once with the last commit information.
>
> I tried:
> stopOnCopy true and false
> limt -1, 0, 1000
> includeMergedRevisions = true and false
> ranges with RevisionRange(Revision.START, Revision.HEAD)
>
> I never receive more than one callback.

I really wish you'd shown actual code, not some description of code ...
it's easier to understand.

> Then I tried something different:
>
> determine maxRev after previous list operation.
>
> ranges = RevisionRange(maxRev + "-0")
>
> and now I get all the versions.
>
> It seems as if the RevisionRange(Revision.HEAD, Revision.START) is not
> being treated as expected.

Actually, it is, but Revision.START is really badly documented ... it's
the same as Revision.UNSPECIFIED and it's only useful in some limited
contexts.

You could try using RevisionRange(Revision.HEAD, Revision.getInstance(0))

-- Brane
Received on 2015-08-19 12:05:01 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.