Poking around some more, I discovered that I need both latest
subclipse (SVNKit based) and latest command line SVN. After that the
local SVN folders can be accessed from both consistently.
Andrus
On Aug 18, 2008, at 11:15 AM, Andrus Adamchik wrote:
I had the same problem this morning. To fix it I downloaded
subversion 1.5.1 from here, and it went away:
http://downloads.open.collab.net/binaries.html
Andrus
On Aug 14, 2008, at 6:43 PM, Michael Gentry wrote:
That was probably it. Our local SVN server was recently updated and
the old Subclipse wouldn't work with it, so I had to update
Subclipse.
I normally update from the command-line for Cayenne, but when I did
so yesterday, I was having build issues and probably did an update
(or
compare/etc) inside Eclipse afterwards trying to get it to build
again.
Thanks!
On Thu, Aug 14, 2008 at 11:29 AM, Dirk Olmes
<[EMAIL PROTECTED]> wrote:
Michael Gentry wrote:
My svn client is 1.4.4:
[10:26:49] ~/Projects/Eclipse/Cayenne30> svn --version
svn, version 1.4.4 (r25188)
compiled Jun 14 2007, 14:23:02
The strange thing is I did an "svn update" yesterday and it worked,
but today it didn't. I can still do updates in Eclipse (using
Subclipse 1.4.x), but I tend to do them from the command-line for
Cayenne since it'll update everything and not just one of the
subprojects. I guess I'll update the command-line ...
Did you update the subclipse recently? If you use subclipse's svnkit
integration instead of the native svn, that might be the cause.
-dirk
