> Thanks for the reply. Is this anything you have any time available to look
> into? If not, we will just have to find some time but it might be a while.
Currently I don't have the time. I will try to fix it if I find the time.
> One of our testers found a couple of other problems that perhaps you can
> shed some light on (we haven't look at them in depth yet).
>
> 1) We authenticate against Windows and the user had changed their AD
> password. When they run Synch, it just gives an error about not being able
> to do it. We finally figured out that it was their password. I do not
> know if the implementation of status in JavaHL just doesn't handle this as
> well as say update and commit, or if the Synch framework just doesn't
> report the error well. We quickly tried to replicate the problem last
> night but couldn't. Update and Commit would fail, but Synch would work!
> Somehow, status must have been using a cache or a cached password. I think
> this was just an anomaly, the main issue I think is just in reporting the
> error better. There wasn't even anything in the console (which make me
> think it is a JavaHL/ClientAdapter issue.
I will check to make sure that the sync functionality uses the same
infrastructure as all other operations, to make sure that we don't
have problems like these again.
> 2) The tester turned on the feature that shows the Revision numbers in the
> Synch view. He observed that remote resources always were showing the HEAD
> revision, as opposed to the last revision they were changed. This is
> confusing. Say you have a file at r50 in your WC, and it is r100 in
> repository. Synch view shows r200 when you are synching. After you do a
> merge, and update your WC shows r100 (correctly). This just confused the
> tester since they had observed the r200 in the Synch view. Where does the
> revision come from, and how can we make it show the file's last changed
> revision?
This is a problem in the 'svn status' command. There is no
getRepositoryLastChangedRevisionNumber in the Status class allthought
there are getRepositoryTextStatus and getRepositoryPropStatus methods.
So I use the revision the current head revision to fill in this
information.
Maybe we should open an enchancement request for this in the
subversion issue tracker or open a discussion in the subversion
mailing list.
Received on Sun Feb 20 03:40:48 2005