I am jumping in kind of late here, but I am pretty sure that Subclipse
makes use of svn cat to retrieve the previous revision and feed it to the
Eclipse compare engine (unfortunately, to get the nice UI of the Eclipse
compare, it cannot just feed it the results of svn diff). Anyway, I
believe that svn cat, when used on a URL, does not have the "follow
history" changes that were added to other commands in 1.1.
There was a recent fix for this made on trunk:
http://svn.collab.net/viewcvs/svn?rev=11688&view=rev
Ben, perhaps you can clarify something for me. As I read some of the
comments, it sounds like svn cat could be fed a WC item, instead of a URL,
but still asked to retrieve the old revision. In other words:
svn cat -r VERY_OLD_REV WC_PATH\item
And in this scenario, svn cat will follow history and retrieve the
contents. If this is the case, perhaps we could modify Subclipse to use
this syntax to get the previous version?
This problem with svn cat causes other problems in Subclipse. If I make a
branch of a project, I cannot checkout the project in Eclipse because
Subclipse does something with svn cat to read the Eclipse .project file in
the branch, and it fails because the file has never been modified on the
branch. I always work around this problem by doing a "dummy" checkout and
commit of the file on the branch using the CLI so that I can then checkout
the whole project in Eclipse.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon Nov 22 12:16:50 2004