You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "corneil.duplessis@gmail.com" <co...@gmail.com> on 2015/08/19 10:48:08 UTC

JavaHL logMessages only one callback

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.

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.

Am I misunderstanding the RevisionRange class?

Corneil du Plessis

Re: JavaHL logMessages only one callback

Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Aug 19, 2015 at 11:18 AM, corneil.duplessis@gmail.com <
corneil.duplessis@gmail.com> wrote:

> 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))
>
>
You want to do the latter if possible.  The server can process -r HEAD:0
significantly faster than it can process -r 0:HEAD


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: JavaHL logMessages only one callback

Posted by "corneil.duplessis@gmail.com" <co...@gmail.com>.
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 <br...@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

Re: JavaHL logMessages only one callback

Posted by Branko Čibej <br...@wandisco.com>.
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