Re: Do Subversion server and client versions need to match for Subclipse to work?

Mark, thank you! I got it to work by upgrading to the site-1.8.22.zip file
from
http://subclipse.tigris.org/servlets/ProjectDocumentList?collapseFolder=2240&folderID=2240.
I think we may have been confused since the page
http://subclipse.tigris.org/servlets/ProjectProcess;jsessionid=1730BA60C1F3F7D88A9C9258C4FC422E?pageID=p4wYuA
says the following about Subclipse 1.8:

Subclipse 1.8.x includes and requires Subversion 1.7.x client features and
working copy format.

I think we thought this meant that you had to have Subversion 1.7 installed
as the client.

After unzipping the site-1.8.22.zip file into my Eclipse dropins directory
and restarting Eclipse, I was able to select File / New / Project / Checkout
Projects from SVN and then extract the svn files locally even though I have
the svn 1.6 client installed locally. When I open a terminal window and
change to the workspace where I extracted the files with the above import, I
see the following:

# svn --version
svn, version 1.6.11 (r934486)
   compiled Mar  4 2015, 05:39:12

# svn info
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy.  Please upgrade your Subversion client to use this
working copy.

So it looks like I cannot run svn commands against this directory with the
local client. The important thing is that I can use the Subclipse plugin in
Eclipse to commit changes with this repository. I tested that and it worked.

So it seems like there must be something about the site-1.6.18 version that
is not compatible with the Eclipse version we have.

Thank you,
Peter



--
View this message in context: http://tigris-scm.10930.n7.nabble.com/Do-Subversion-server-and-client-versions-need-to-match-for-Subclipse-to-work-tp100368p100375.html
Sent from the subclipse - users mailing list archive at Nabble.com.

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3164731

To unsubscribe from this discussion, e-mail: [[email protected]].