subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "corneil.duplessis@gmail.com" <corneil.duples...@gmail.com>
Subject Re: JavaHL logMessages only one callback
Date Wed, 19 Aug 2015 15:18:35 GMT
Thanks, the following worked and only difference was the order of the
callbacks.

RevisionRange(Revision.getInstance(0), Revision.HEAD)
RevisionRange(Revision.HEAD, Revision.getInstance(0))



Corneil du Plessis
about.me/corneil


On 19 August 2015 at 11:04, Branko ─îibej <brane@wandisco.com> wrote:
>
> On 19.08.2015 10:48, corneil.duplessis@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

Mime
View raw message